Sunny
7/22/2004 10:13:00 PM
Ok, one way or another, the client have to know about the server class,
or its interfaces. If your concern is not having more than 1 file to
distribute, and if you do not want to ship the server code (even
included as a part of the client), than the only way to go is to use an
interface or abstract class approach. Just include its implementation in
the client.
Than, at the server you have to have a copy of the client.exe, and
reference to it. Unfortunately VS.Net does not allow you to create a
reference to .exe, but as far as the .exe is assembly as well, the
commandline c# compiler allows it.
So, you can achieve what you want on the price of manual compilation :)
Sunny
In article <uBzPMBDcEHA.3596@tk2msftngp13.phx.gbl>, jon.turner@mail.com
says...
> I have a client that calls into a Remote Server hosted in IIS.
> I don't want to have to distribute the Remote Server DLL, or
> a Proxy DLL with the Client. What can I do to accomplish this.
>
> 1. If I reference the Remote DLL in the Client Project, the DLL
> must be resident on the Client machine. (don't want this)
>
> 2. If I use SoapSuds to generate a Proxy DLL, the proxy DLL
> must be resident on the Client machine also. (don't want this either)
>
> I just want to distribute the Client Exe.
>
> Many Thanks
>
>
>