Just a little reminder for my own sake...
Unrecognized endpoint to WCF Test Client
If you have installed the Biztalk Services SDK on top of VS 2008 SP1, the Biztalk Service SDK introduces an endpoint with relayBinding in the <client> section of the <system.serviceModel> element in the machine.config file.
When adding a service to WCF Test Client, an unrecognized endpoint will be generated whose contract is IMetadataExchange. Then Test Client will report error: “The contract ‘IMetadataExchange’ in client configuration does not match the name in service contract…”. The screenshot is attached below:
After you click “OK”, the service node will appear in the tree with the redundant “IMetadataExange (sb)” section. There is no impact for the functionalities.
The screenshot is attached below:
If you will frequently add services to WCF Test Client, there is a work around to avoid the inconvenient error message:
When you run the WcfTestClient, modify the machine.config file (located in \WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG) by commenting out the <client> section below that is nested in the <system.serviceModel> element. Re-enable the section when you use the Biztalk Services SDK.
<client>
<endpoint address="" binding="relayBinding" bindingConfiguration="metadataExchangeRelayBinding"
contract="IMetadataExchange" name="sb" />
</client>
<bindings>
<relayBinding>
<binding name="metadataExchangeRelayBinding" />
</relayBinding>
</bindings>
Comments
- Anonymous
November 04, 2008
PingBack from http://mstechnews.info/2008/11/just-a-little-reminder-for-my-own-sake/ - Anonymous
February 21, 2012
That is NOT a solution. i use BT services all the time and cannot keep commenting out my MACHINE.CONFIG