How to: Configure a Remoting Client in IIS

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

The following example configures a remoting client in IIS. The url attribute in the <client> tag points to the location of the remote application. This is the location the application will use when it needs a client-activated object. Each server-activated object has a specific URL pointing to the location of the object.

Example

<configuration>
   <system.runtime.remoting>
      <application>
         <client 
            url = "http://www. cpandl.com"
            displayName="MyApplication"
         >
            <wellknown 
               type = "myType,myAssembly"
               url = http://www. cpandl.com/myType.soap"
            />
            <activated 
               type = "myClientActivatedType,myAssembly"
            />
         </client>
      </application>
   </system.runtime.remoting>
</configuration>

See Also

Reference

System.Runtime.Remoting.RemotingConfiguration Class

Concepts

Client-Side Registration
Configuration of Remote Applications
Remote Object Configuration

Other Resources

Registering Remote Objects Using Configuration Files
.NET Framework Remoting Overview