Client-Side Registration
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).
Server-activated and client-activated objects are normally registered in a client application configuration file inside the <client> element to identify remote objects that your application uses. Both server-activated (<wellknown>) types and client-activated (<activated>) types can be specified, but the <wellknown> client instance element supports different attributes than when it is specified under the <service> element. Inside a <client> element, a <wellknown> element can only contain displayName, type and url attributes; any other attributes will raise an exception.
Configuring a Remoting Client In IIS
If you intend to consume remote services from an ASP.NET application or .NET remoting application hosted in IIS, you must use the Application_Start handler in the Global.asax file to load your configuration file using RemotingConfiguration.Configure() and passing the name of your configuration file. If you place client information in the Web.config file, it will not be picked up automatically, as it is in the case of configuring the server in IIS.
See Also
Tasks
How to: Configure a Remoting Client in IIS
Reference
System.Runtime.Remoting.RemotingConfiguration Class
Concepts
Configuration of Remote Applications
Remote Object Configuration
Other Resources
Registering Remote Objects Using Configuration Files
.NET Framework Remoting Overview