dotnet remoting: I have a class ClassA that needs to be remoted to another server in order to
have access to the resources necessary to do its job. One or more of its
methods needs to return an instance of another class ClassB. ClassB has no
remoting requirements, but I'm not clear if it's possible for Remote ObjectA
to instantiate and return instances of ClassB and have those instances not
be remote objects. Can this be done? If so, how? Is it simply a matter of
marking ClassB as serializable so that instances of ClassB are actually
copied from the remote server to the client? And in that scenario I assume
that the assembly that defines ClassB needs to exist on both the remote
server and the client?

Thanks for any help.

Zoe

[quoted text, click to view]

Yes

[quoted text, click to view]

Yes

[quoted text, click to view]