When starting to debug a new WCF service I received the following error message:
“The contract ‘IMetatdataExchange’ in client configuration does not match the name in service contract, or there is no valid method in this contract.”
I had added my MEX endpoint in the web.config and was able to review the service WSDL through a browser, so I was really not sure why I was getting this. As it turns out, this error message is caused by an entry in the machine.config for an endpoint declaration defined like this:
<endpoint address="" binding="netTcpRelayBinding" contract="IMetadataExchange" name="sb" />
I’ve commented it out for now and the WCF Test Client is now able to properly interrogate the service metadata without giving me an error.
After a bit of Google’ing this error, I found this explanation from Joel C on StackOverflow.com. Looks like at some point an installation for the .NET Service SDK (which I don’t remember installing) updated the machine.config with that information.
For now, it works having removed it.
No comments:
Post a Comment