I have a problem where WCF is reporting...
net.pipe://192.168.0.100/SystemA/Service1.svc/mexPipe' could not be activated.
I have defined my base addresses as follows:
Service 1...
<baseAddresses>
<add baseAddress="http://192.168.0.100:8050/ProductsService/Service1.svc" />
<add baseAddress="net.tcp://192.168.0.100:8051/ProductsService/Service1.svc" />
<add baseAddress="net.pipe://192.168.0.100/ProductsService/Service1.svc" />
</baseAddresses>
Service 2...
<baseAddresses>
<add baseAddress="http://192.168.0.100:8050/ProductsService/Service2.svc" />
<add baseAddress="net.tcp://192.168.0.100:8051/ProductsService/Service2.svc" />
<add baseAddress="net.pipe://192.168.0.100/ProductsService/Service2.svc" />
</baseAddresses>
For each service I then define Mex endpoints as follows...
<endpoint address="mexPipe" contract="IMetadataExchange" binding="mexNamedPipeBinding" />
This should surely give me 2x mex endpoints as follows...
net.pipe://192.168.0.100/ProductsService/Service1.svc/mexPipe
net.pipe://192.168.0.100/ProductsService/Service2.svc/mexPipe
However I dont think that this is working looking at this post...
net.tcp binding metadata problem
The poster appears to have a similar configuration to me and the responder states that the base addresses are not "unique" within each scheme - but surely they are as they both reference two unique services?
Can WCF detect that my mex end points are netNamedPipe and look up the base address for them? Given that the binding is "mexNamedPipeBinding" - or doesnt this work?