Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

Advanced Design Issues 

Because the type information of a remote type is required by the client, it is often easiest to simply deploy the remote type assembly on the client. However, in many cases you will 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 will be shared by the server and the client.

    NoteNote

    The client will have to call GetObject to instantiate the proxy. Using the operator new will cause 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 Using Soapsuds.exe with Remoting.

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

See Also

Community Additions

ADD
Show:
© 2015 Microsoft