Export (0) Print
Expand All

Accessing Serviced Components Remotely 

.NET Framework 2.0

Serviced components all derive from MarshalByRefObject and therefore can be accessed from remote clients. Serviced components can be accessed remotely in the following ways:

  • A serviced component can be hosted in ASP.NET, which offers good security, interoperability, and encryption options, along with known scalability and performance. For an example of this, see "Web Services" in O COM+, (In this article, "Web Services" refers to ASP.NET Web Services.)

  • COM+ Web Services adds features that integrate with Microsoft .NET Framework remoting to provide check box activation of XML Web service publication using SOAP for serviced components. For more information, see COM+ Web Services: and "Web Services" in .NET Enterprise Services and COM+ 1.5 Architecture. (In this article, "Web Services" refers to COM+ Web Services.)

  • A serviced component can be hosted in Dllhost and accessed using Distributed COM (DCOM). This option offers optimal performance and security, and the ability to pass service contexts across computers. For more information, see "Remote Components" in Understanding Enterprise Services (COM+) in .NET.

The main consideration when choosing how to access serviced components remotely is whether the services must flow across computers. For instance, you must use DCOM if the client and server both reside within a server farm, and a transaction is created on one computer and must continue on another computer. However, if clients simply have to call a remote serviced component, then COM+ Web Services is a good alternative.

For more information on choosing between methods of remote access, see:

See Also

Community Additions

© 2014 Microsoft