Registering Remote Objects Using Configuration Files

This topic is specific to a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using the  Windows Communication Foundation (WCF).

Remote objects can be registered either programmatically or by specifying the remote objects in configuration files. Registering remote objects in configuration files allows administrators of applications that expose or consume remote objects to change the location of the objects without recompiling the application. This section describes how to register remote objects in configuration files.

In This Section

  • Remote Object Configuration
    Describes the basic requirements of using an application configuration file with .NET remoting, including lifetimes and instance and template elements.
  • Server-Side Registration
    Describes the configuration requirements of an application that is publishing remotable types.
  • Client-Side Registration
    Describes the configuration requirements of an application that is consuming remotable types.
  • Channel Registration
    Describes the configuration requirements of channels and channel sink providers.

Reference

  • System.Runtime.Remoting
    Provides reference documentation for the System.Runtime.Remoting namespace, which contains classes and interfaces that allow developers to create and configure distributed applications.
  • Configuration of Remote Applications
    Describes the configuration requirements of .NET remoting, whether you use a configuration file or configure your applications programmatically.

Build Date: 2011-02-07