This thread indicates that there is a known bug concerning reuse of service contract interfaces with WCF. Has this bug been solved?
I would like to avoid using the workaround since it would mean rewriting a whole lot of client code.
In my specific scenario, I have a rather complex setting with 3 solutions: A server, a client and a third application. I want to reuse some of the logic from my server and the controls from my client in my third application, but I don't want to have to setup
a server simply for the amount of logic I reuse. My idea was to instanciate the class that imlpements the service contract in the application, and link up the controls with the instance of the service that runs in the same application. This isn't working because
the controls expect a reference to the service contract interface proxy and not the actual service contract interface. Even using the /r switch (which I assume is the "reuse types in referenced assemblies" checkbox in VS), the service proxy is created and
the controls won't compile because of type mismatch.
What am I doing wrong?
Thank you for your time.
View Complete Post