The .NET Framework provides many types to support building enterprise systems, defined under the namespace System.EnterpriseServices. The first release of .NET depends on COM+ to provide the needed enterprise services.
A .NET component that uses .NET/COM+ services is called a serviced component. Developing a serviced component is a four-step process:
A client uses a serviced component object just as any other .NET object. The important thing to remember is to dispose the object after its use.
The .NET/COM+ plumbing provides many enterprise services. In this chapter we looked at some frequently used services such as JIT activation, object pooling, role-based security, queued components, and transaction support.
The COM+ infrastructure offers some other services such as synchronization, loosely coupled events, shared properties, and so on, that I haven't covered in this chapter. In particular, I haven't covered COM+ synchronization services, as .NET provides the same service natively. You should be able to use any other COM+ services using the .NET SDK documentation as a reference, combined with your knowledge of serviced components from this chapter. Interested readers may also wish to look at [EWA-01], [And-02], and [Mcc-02] to supplement their knowledge.
52.15.59.163