Object type. Must be .NET or dotnet for .NET objects.

Name of the .NET class to represent as an object.

For local .NET assemblies, the absolute path or paths to the assembly or assemblies (.exe or .dll files) from which to access the .NET class and its supporting classes. If a class in an assembly requires supporting classes that are in other assemblies, you must also specify those assemblies. You can, however, omit the supporting assemblies for the following types of supporting classes:

• .NET core classes (classes in mscorlib.dll)
• classes in assemblies that are in the global assembly cache (GAC)

To specify multiple assemblies, use a comma-delimited list.

For remote .NET assemblies, you must specify the absolute path or paths of the local proxy JAR file or files that represent the assemblies.

If you omit this parameter, and there is no local .NET installation, the function fails without generating an error. If you omit this parameter, there is a local .NET installation, and the specified class is not in the .NET core classes, ColdFusion generates an error.

Host name or IP address of the server where the .NET-side agent is running. Can be in any of these forms:

• server name (for example, myserver)
• IP address (for example, 127.0.0.1)

You must specify this attribute to access .NET components on a remote server.

Port number at which the .NET-side agent is listening.

Protocol to use to use for communication between ColdFusion and .NET. Must be one of the following values:

• http: Use HTTP/SOAP communication protocol. This option is slower than tcp, but might be required for access through a firewall.
• tcp: Use binary TCP/IP protocol. This method is more efficient than HTTP.

Whether to secure communications with the .NET-side agent. If true, ColdFusion uses SSL to communicate with .NET.