I'm sorry if this question has been asked/answered before on this forum. I have searched both here and on the web in general, but to no avail as yet...
I am running VS2010 and .Net 4, so in theory have all the latest versions of everything at my disposal.
I have an executable a.exe. This downcalls into a dll
b.dll. b.dll wants to send an MSMQ message using WCF. For cleanness (a.exe is a generic service and knows nothing about WCF) I want to define the client endpoint in
b.dll.config. However I am finding that WCF is insisting that the information is held in a.exe.config.
The exact problem is that when I create my proxy (i.e. the class which derives from ClientBase<T>), I get the message
Could not find endpoint element with name 'XXX' and contract 'YYY' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found
in the client element.
From what I have seen I have just described an extremely common problem that people have had with WCF over the years. My questions is basically to find out, given that I have WCF 4 at my disposal, whether there is now a standard approach to this
Things I have tried so far:
The obvious one...putting all my config info in a.exe.config. When I do this, everything works file, so I
View Complete Post