Building a Basic .NET Framework Remoting Application

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).

Building an application that uses .NET Framework remoting to communicate across application domain boundaries is very straightforward. You must have an implementation of a remotable type, a listening or host application domain, a client or calling application domain, and you must configure the remoting system in each application domain to use remote activation for the remotable type. This process applies no matter how complex your remoting scenario becomes.

In This Section

• How to: Build a Remotable Type
  Describes how to build a remotable type.

• How to: Build a Hosting Application
  Describes how to build a host application that listens for remote clients of a remotable type.

• How to: Build a Client Application
  Describes how to build an application that creates an instance of your remotable type and accesses designated members.

• How to: Compile and Run a Basic Remoting Application
  Describes how to compile and run the application.

• How to: Specify a Channel in a Configuration File
  Describes how to change the channel type in the configuration file.

• Basic Remoting Task List
  Describes how to build and execute applications that use .NET Framework remoting.

Reference

• System.Runtime.Remoting
  Provides classes and interfaces that allow developers to create and configure distributed applications.

Related Sections

• Configuration of Remote Applications
  Describes the information .NET Framework remoting system requires to make remote calls work.

• Remoting Examples
  Provides several complete sample applications that use different elements of the remoting infrastructure.