System.Runtime.Remoting Namespace
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Provides classes and interfaces that allow developers to create and configure distributed applications. Some of the more important classes of the System.Runtime.Remoting namespace are the RemotingConfiguration class, the RemotingServices class, and the ObjRef class.
Classes
| Name | Description |
|---|---|
| ObjectHandle |
Wraps marshal-by-value object references, allowing them to be returned through an indirection. |
Remarks
The RemotingConfiguration class contains static methods for interfacing with configuration settings. The RemotingConfiguration.Configure method allows developers to configure the remoting infrastructure through the use of XML formatted configuration files. The RemotingConfiguration class also contains several methods for client-end and server-end registration of client and server activated objects that reside on the server.
The RemotingServices class provides a number of methods to help in using and publishing remoted objects. The RemotingServices.Marshal method provides the functionality for storing all the relevant information required to activate and communicate with a remote object in an instance of the ObjRef class for later serialization and transmission to a remote location. The RemotingServices.Unmarshal method reverses this process, creating a proxy for a remote object that can be used by an application without regard for any remoting subdivisions.
The ObjRef class holds all the relevant information required to activate and communicate with a remote object. This class is a serializable representation of an object that is transmitted to a remote location using a channel, where it is unmarshaled (see Unmarshal) and can be used to create a local proxy of the remoted object.
Note
Marshal-by-reference objects (MBRs) do not reside in memory forever. Instead, unless the type overrides MarshalByRefObject.InitializeLifetimeService to control its own lifetime policies, each MBR has a finite lifetime before the .NET Framework remoting system begins the process of deleting it and reclaiming the memory.
