Export (0) Print
Expand All

Advanced Design Issues

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

Because the type information of a remote type is required by the client, it is often easiest to deploy the remote type assembly on the client. However, in many cases you do not want the client to have access to the implementation of the type. There are a number of ways to solve this problem:

  • Declare an interface in an assembly that is shared by the server and the client.

    y1611dh0.note(en-us,VS.90).gifNote:
    The client must call GetObject to instantiate the proxy. Using the operator new causes a compilation error because you cannot create an instance of an interface.

  • Generate a metadata assembly using the Soapsuds tool. For more information, see Using Soapsuds.exe with Remoting.

  • Generate source code using the Soapsuds tool. For more information, see Using Soapsuds.exe with Remoting.

See Also

Community Additions

Show:
© 2014 Microsoft