All geek questions in one place

WCF and moving proxy code in a DLL. Is it possible?

it seems like I cannot successfully move my WCF proxy code to a separate DLL (unlike the EXE, as I see in all the examples that I used).

The reason I'm trying to do this is because I would like my proxy code to be called by different clients (possibly unmanaged code), which may not know anything about WCF, but just have to access the services (via Facade maybe?).

Whenever I move the following code that creates a new proxy for another VS project within the same solution, I get the scary "Could not find the default endpoint element that refers to the localhost.IRemoteCommandService contract in the configuration section ServiceModel "exception.

localhost.RemoteCommandServiceClient proxy = 
    new localhost.RemoteCommandServiceClient();

The same code runs smoothly whenever it is used in the main method in the same project as the proxy code (automatically generated from Visual Studio).

Any idea? I hope that the client code of my proxy should not have the configuration of the XML service model as a proxy server, because this can lead to a target hit. First of all, I move the WCF proxy code to a DLL.

Thanks Stefano

+3
2

, -, .

- , one, serviceModel ,

+2

. serviceModel app.config - (.. , , .. ).

+4

Source: https://habr.com/ru/post/1706719/

More articles:


All Articles