WCF duplex communication with unique client-side callback addresses

When doing duplex communication in WCF - e.g. using the wsDualHttpBinding - the WCF runtime automatically sets up a callback address for the calling application to listen on based on a value provided in a binding configuration. This is a unique address, unique per machine. If you want to run several client applications (and if it is just for testing purposes) it is necessary to have a really unique client-side callback address per application instance. And uniqueness cries for GUIDs.
Following is an app.config for the client together with a code snippet to set up up application instance-specific callback addresses.

 

<configuration>
 <system.serviceModel>
  <client>
   <endpoint name="Duplex"
    address="http://localhost/TecTvDuplex" 
    binding="wsDualHttpBinding" 
    bindingConfiguration="customizedCallbackBinding" 
    contract="ITecTv" />
  </client>
  <bindings>
   <wsDualHttpBinding>
    <binding name="customizedCallbackBinding" 
     clientBaseAddress="http://localhost:7777/TecTvClient/" />
    </wsDualHttpBinding>
  </bindings>
 </system.serviceModel>
</configuration>

[...]

WSDualHttpBinding binding = (WSDualHttpBinding)proxy.Endpoint.Binding;
string clientCallbackAddress = binding.ClientBaseAddress.AbsoluteUri;
clientCallbackAddress += Guid.NewGuid().ToString();
binding.ClientBaseAddress = new Uri(clientCallbackAddress);

Comments

[Buddhike]

testing...

[Buddhike]

testing