How to: Register a Server-Activated Object and a Client-Activated Object for a Host Application Domain

  • Article

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 shows how to register a server-activated object and a client-activated object for a host application domain. The type attribute in the <activated> tag indicates the full type name and assembly name of the object, as it appears in the <wellknown> tag. 

Example

<configuration>
   <system.runtime.remoting>
      <application>
         <service>
           <wellknown
             mode = "SingleCall" 
             type = "myType,myAssembly"
             objectUri = "myType.soap"
           />
           <activated
             type="MyActivatedType, TypeAssembly"
           />
         </service>
      </application>
   </system.runtime.remoting>
</configuration>

See Also

Reference

System.Runtime.Remoting.RemotingConfiguration Class

Concepts

Server-Side Registration
Configuration of Remote Applications
Remote Object Configuration

Other Resources

Registering Remote Objects Using Configuration Files
.NET Framework Remoting Overview