The config file supports installing multiple files in a package and the configuration of all three levels of COM+ objects hierarchy: the package, the components and the interfaces. It attempts to cover all the desired COM+ attributes otherwise available via the COM+ MMC user interface or the COMAdmin library. Additionally, once the configuration file is created, the deployment becomes a one liner in a similar way to how serviced components are registered using RegSvcs: all you need to specify is the path to the config file, and the utility will do the rest.Įxample: RegComPlus.exe %binpath%\nfig > %logfile% The Config File (Advanced Mode)
COMAdmin based VBS scripts is that the deployment stays simple and easy to maintain: The complex COM+ configuration code is encapsulated in the utility, and changing the desired configuration does not require coding skills. The advantage of using a configuration file vs. More details on the configuration file is available below. The configuration file attempts to cover all the desired COM+ attributes otherwise available via the COM+ MMC user interface or the COMAdmin library.
Such COM+ packages require additional configuration information that is not accessible to the registration utility this is where a configuration file comes into play. server) packages, or packages that include multiple DLLs, or packages that require specific configuration of components and/or of interfaces. These are registered in a similar way to how service components are registered using RegSvcs: all you need to specify is the path to the DLL and the package name, and the utility will do the rest.Įxample: RegComPlus.exe %binpath%\example.dll ComPlusPackageName > %logfile%Īdvanced mode: Designed for out of process (a.k.a. library) packages, using “all default” COM+ configuration. The lack of inline annotated COM+ configuration attributes in COM based languages like C++ and VB make life a bit more difficult, which is why the utility has two modes:īasic mode: Designed for inproc (a.k.a. The suggested solution in this article is a command line utility which allows an easy, one line, registration of COM components in COM+. Things become more uncomfortable when you try to utilize a modern deployment tool which tend to like the command line approach over the MSI one.
NET serviced components are deployed using a simple command line script, the veteran COM component deployment requires that either MSIs or a series of more complicated VBS scripts (COMAdmin based) are put together. NET/COM environment challenging: While the. The differences noted above make the deployment in a mixed. In this scenario, the assembly's dependencies are expected to coexist in the same folder or GAC, and COM+ configuration attributes are annotated inline using EnterpriseServices custom attributes. Serviced Components are registered using the framework provided RegSvcs utility. NET introduced the idea of command line deployment. A typical DNA deployment scenario included a series of MSIs representing multiple COM+ packages, and a master MSI or installation script to bind them all. The latter were created using the COM+ export function or other tools like Orca, and included the component DLL(s), their dependencies (other DLLs, TLBs), and the COM+ configuration attributes for the package, components, and interfaces. In the good old days of DNA, COM+ components where registered using MSIs.
Such a tool simplifies the deployment of such mixed technologies by allowing a full command line based deployment. NET/COM COM+ based environment, one may find a need for a command line tool to deploy COM components in COM+.