Building a webservice using .NET Remoting?

[Hani Atassi]

I have the WebService (Server) class hosted under IIS. The Webservice is a class derived from MarshalByRefObject. The file web.config is setup to let IIS load the server class when it's called.

I built the client application successfully, but it works only if I reference the WebService library (not web reference but regular DLL reference). I am using RemotingConfiguration.Configure("myfile.exe.config") to configure the client to connect to the webservice. As I believe also, the proxy is being built runtime and then used.

I don't understand why I need to reference the webservice assembly inside my client. Did I do anything worng?

Thanks,

[koolsuccess]

I have the same exact issue:

My client had my remoting object referenced by DLL, but I need the client to access the object as a webservice created using IIS

Please help
Travis

[Arjay]

The thread you responded to is 8 years old.

At any rate, if you use .Net remoting, you'll need to make the remoting object available on the client. With .Net remoting the binary object is passed around between the client and server, so the object needs to be available on both sides.

If you use web service, you generate a proxy that the client uses (and the code remains decoupled).