Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy does the WCF Test Client tool only display a single endpoint baseAdress for multiple endpoints when debugging?
    text
    copied!<p>I have the following configuration for my Windows Service hosted WCF service:</p> <pre><code> &lt;services&gt; &lt;service name="MyService" behaviorConfiguration="MyServiceBehavior"&gt; &lt;endpoint address="" binding="netTcpBinding" bindingConfiguration="WindowsClientOverTcp" name="WindowsClientOverTcp" contract="IMyService" /&gt; &lt;endpoint address="" binding="wsHttpBinding" bindingConfiguration="WindowsClientOverHttps" name="WindowsClientOverHttps" contract="IMyService"&gt; &lt;/endpoint&gt; &lt;endpoint address="mex" binding="mexTcpBinding" contract="IMetadataExchange" /&gt; &lt;endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange" /&gt; &lt;host&gt; &lt;baseAddresses&gt; &lt;add baseAddress="https://MyMachine:8250/Services/MyService/Https" /&gt; &lt;add baseAddress="net.tcp://MyMachine:8250/Services/MyService/tcp" /&gt; &lt;/baseAddresses&gt; &lt;/host&gt; &lt;/service&gt; </code></pre> <p>1st: Everything works. However I have a question. When starting to debug the service in VS.NET 2010 and the "WCF Test Client" tool appears, only the single "net.tcp://MyMachine:8250/Services/MyService/tcp" address is displayed at the top of the tree navigation, and both endpoints displayed as child elements (WindowsClientOverTcp &amp; WindowsClientOverHttps). Now <em>both</em> base addresses are consumable <em>and</em> usable so there is no major issue. However, why is it only showing the single address in the tool? I thought it might be the order displayed in the .config so I switched them around but that didn't change anything.</p> <p>Anyone know why both base addresses do not display in the WCF Test Client tool when having a single service exposing multiple endpoints?</p> <p>Thanks!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload