Share via


ProtocolDefinition.AssemblyName Property

Gets or sets the path and file name of the assembly that contains the protocol class.

Namespace: Microsoft.SqlServer.Management.Nmo
Assembly: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Syntax

'Declaration
Public Property AssemblyName As String
public string AssemblyName { get; set; }
public:
property String^ AssemblyName {
    String^ get ();
    void set (String^ value);
}
/** @property */
public String get_AssemblyName ()

/** @property */
public void set_AssemblyName (String value)
public function get AssemblyName () : String

public function set AssemblyName (value : String)

Property Value

A String, between 1 and 260 characters in length, that specifies the name of the assembly.

Remarks

You must specify either the full path and file name of the assembly or the assembly's strong name.

For custom delivery protocols based on the IHttpProtocolProvider interface, do not use the AssemblyName property.

If you do not know the class and assembly names for a custom protocol, contact the developer or supplier who provided the custom delivery protocol. The assembly name is usually the name of a DLL containing the custom delivery protocol implementation and the class name is the class within the assembly for the protocol.

Example

The following examples show how to declare a custom delivery protocol and add it to an instance of Notification Services:

ProtocolDefinition customProtocol = 
    new ProtocolDefinition(myInstance, "MyCustomProtocol");
customProtocol.ClassName = "MyNamespace.MyProtocolClass";
customProtocol.AssemblyName = @"C:\NS\Full\MyCustomComponents.dll";
myInstance.ProtocolDefinitions.Add(customProtocol);
Dim customProtocol As ProtocolDefinition = _
    New ProtocolDefinition(myInstance, "MyCustomProtocol")
customProtocol.ClassName = "MyNamespace.MyProtocolClass"
customProtocol.AssemblyName = _
    "C:\NS\Full\MyCustomComponents.dll"
myInstance.ProtocolDefinitions.Add(customProtocol)

Thread Safety

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Platforms

Development Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

Target Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

See Also

Reference

ProtocolDefinition Class
ProtocolDefinition Members
Microsoft.SqlServer.Management.Nmo Namespace

Other Resources

Defining Custom Delivery Protocols
AssemblyName Element (ICF)