Dynamically Registering an Assembly

The simplest way to deploy a serviced component application is with dynamic registration, which consists of copying an assembly containing one or more serviced components to the COM+ application's directory. Assemblies that are dynamically registered are not placed in the global assembly cache.

Note   Assemblies placed in the global assembly cache require manual registration.

Dynamic registration enables managed clients, such as ASP.NET and Web Form clients, to call serviced components that are unregistered. The first time a client tries to create an instance of a serviced component, the common language runtime registers the assembly, the type library, and configures the COM+ catalog. Registration occurs only once for a particular version of an assembly.

**Note   **If you create a server application, the assembly and any assemblies on which it depends must be added to the global assembly cache (GAC) by using Windows Installer before the server application can be used; otherwise, the application generates an exception.

To deploy an application called by Web Form clients, you must copy the assembly files to the \bin directory of the virtual root of the Web application.

To deploy any server application that is called by COM clients, you must register the assembly manually.

Note   The application user must be a member of the Administrator group.

See Also

Registering Serviced Components | Manually Registering an Assembly | System.EnterpriseServices Namespace | Extending Metadata Using Attributes | System.EnterpriseServices Namespace