COM+ Configured Components
COM+ allows you to import only in-proc (DLL) components. You cannot import COM components that reside in a local server (EXE); COM+ lets you configure the activation type of your application, server, or library. In the case of a library, the client simply loads the original DLL into its process and uses the component. If you configure the application to be a server application, COM+ promotes your original DLL to become a local server by hosting it in a surrogate process of its own. However, COM+ cannot make a library application out of a COM local server. In addition, many COM+ services require explicit process-level administration that the local server’s code simply does not contain.
Once an in-proc component is imported to COM+, it is called a
configured component to emphasize the fact that
much component functionality and behavior is actually configured and
administered outside the component. A classic COM component (be it
in-proc or local) that has not been imported into COM+ is called a
nonconfigured
component.
Configured and
nonconfigured components can interact freely and call each
other’s interfaces. The configured component must reside on a
Windows 2000 machine, but the client of a configured component can
reside on any Windows-family machine, such as Windows NT, Windows Me,
or Windows 9x.
Configuration lets you control the way your application, component, interface, or method behaves under COM+. The COM+ development paradigm lets COM+ manage ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access