COM+ 1.0 run-time services make it easier for you to create distributed applications that are timely and cost-effective. These services work on your application's behalf to manage transaction processing, object pooling, threading, security, and each object's lifecycle.
A NGWS class can request COM+ 1.0 services, providing that you have prepared the class to do so. The table below identifies the sequence of actions required to mark a managed type so that it can access services.
Type of Action | Description |
---|---|
Decision | Identify the services you intend to include in your application.
See COM+ 1.0 Services for a summary of services and links to additional information. |
Programming task | Add the COMEmulate custom attribute to your class. Classes must include this attribute to expose COM+ 1.0 services.
See Marking a ComEmulate Custom Attribute for additional information. |
Programming task | Declare services programmatically by inserting the service-related attribute in the emulated class. The RegSvcs utility configures the service for you.
See Marking a ComEmulate Custom Attribute for a sample. You can omit this step and configure services manually after registering your class. Some services, such as object pooling, must be configured manually. |
Programming task | Access and control services programmatically with interfaces, methods, and properties in the Microsoft.ComServices namespace.
For example, you can direct an object to commit or abort a transaction by adding the SetComplete or SetAbort members to the internal class. See Marking a ComEmulate Custom Attribute for a sample of this implementation. |
Administrative task | Run the RegSvcs utility to load, register, and configure NGWS classes. This command-line utility combines several tasks into a single step. |
Administrative task | Use the Component Services snap-in administrative tools or write a script to manually configure any COM+ 1.0 services.
See the COM+ 1.0 Programming Guide for instructions on configuring individual services. |