What is a serviced component and what should I consider when creating one?
A .NET component that uses COM+ services is referred to as a serviced component. When you create serviced components you should consider the following: • When an instance of a serviced component is no longer needed, the client should call the Dispose() method to free the resources used by the component. • The serviced component must contain a default constructor (a constructor with no arguments). • Static methods are not remotable and are not associated with a particular instance of a class; therefore, they cannot take advantage of any of the COM+ services such as transactions and object pooling. • Those services that flow between computers, such as transactions and Windows authentication, only do so when DCOM is used. • At run time, the user executing the COM+ application must have permission to run unmanaged code. The ServiceComponent class, in the System.EnterpriseServices namespace, is the base object of all classes using COM+ services. To deploy and use a ServicedComponent object
Related Questions
- Where can we get additional training time in creating common tasks, since they are an important component of the secondary reform work in all core subject areas?
- When creating a new CPE Name, what term should be used if a given component is not defined by a vendor?
- What is a serviced component and what should I consider when creating one?
