I successfully implemented a WCF Service hosted in a Windows Service a few days ago. The community here at StackOverflow helped me with the WSDL exposure here. I thank you once again. However recently I found out that there is another potential client for this service this time located on the same machine as the service and this lead me to think I should add another endpoint with the namedPipesBinding.
Named pipes seem to be the best solution for intra-machine communication as far as I am concerned. Please correct me if this is wrong.
I need to expose another endpoint for the same service/contract but this time using a netNamedPipeBinding. However I really don't understand how do I can then add a service reference from a client. Foolishly after adding
<endpoint address="net.pipe://localhost/OfficeService" binding="netNamedPipeBinding" contract="netBridge.Development.OfficeService.IWordService" bindingConfiguration="localBinding" />
I have tried to add a service reference in a Windows Forms Application located on the same machine typing the net.pipe://…. url. It didn't work. I must mention I have removed the mex (MetaData Exchange) endpoint earlier because I considered it not necessary.
- Is this mex endpoint necessary for named pipes endpoint binding discovery?
- How should I add a service reference in the client app to the named pipe endpoint?