This Kalani book … old  … I like it … MCAD/MCSD Training Guide (70-320): Developing XML Web Services and Server Components with Visual C# .NET and the .NET Framework

Chapter 7 is on Serviced Components. Here are some thoughts … take them with a grain of salt.

I think the only reason you want to use a serviced component is to access COM+ services, such as transactions, object pooling, and JIT. The Kalani book has an example (StepByStep7-1) that creates and uses a serviced component but uses none of these features. The example succeeds in showing you how to create and use a serviced component but fails in that there is no motivation for doing so. You keep loooking at the code and saying, Why do this?

The example goes on in StepByStep7-2 to get a strong name for the assembly and in StepByStep7-3 to install it into the COM+ catalog. Then, StepByStep7-4 show how to manage the component with the Component Services Admin Tool. But you know you never actually use this serviced component.

A serviced component doesn’t actually get used until StepByStep7-7. This step shows code that calls a serviced component made in StepByStep7-5, which is just like StepByStep7-1, except that it has a ClassInterface attribute and a custom interface. The serviced component derives form this interface as well as ServicedComponent. But again, the example uses none of the features that would motivate you to using a serviced component in the first place.