Enterprise Services


Component Services exposes a rich set of features that you can consume from .NET by having your types inherit from ServicedComponent and decorating your types with attributes that determine how they’ll be configured when they’re registered with COM+.

Because this is still a COM-based technology, a layer of interop is used; therefore, you must be sure the benefits of the features you’re leveraging outweigh the performance hit you’ll incur by using the environment. Many of the features of COM+, when needed, will be worth this performance hit.

Once your components are created and configured within COM+, calling processes will need to get to them. This may happen in process from IIS, it may happen via DCOM from a Windows Forms application, or it may happen via Web Services. In the next chapter, we’ll examine some of the different options that are available for invoking Serviced Components from within different application architectures.


Method Call Component Service Enterprise Service Security Context Public Class 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Dominic Selly, Andrew Troelsen, and Tom Barnaby 2006

Personalised recommendations