title: Expose a WCF Service through a Named Pipes binding
body: <h2>Intro:</h2>
  
  <p>I successfully implemented a WCF Service hosted in a Windows Service a few days ago. The community here at StackOverflow helped me with <a href="https://stackoverflow.com/questions/167852/wsdl-url-for-a-wcf-service-basichttpbinding-hosted-inside-a-windows-service">the WSDL exposure here</a>. 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.</p>
  
  <p>Named pipes seem to be the best solution for intra-machine communication as far as I am concerned. <strong>Please</strong> correct me if this is wrong.</p>
  
  <h2>Problem:</h2>
  
  <p>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 </p>
  
  <pre><code>&lt;endpoint address="net.pipe://localhost/OfficeService"
            binding="netNamedPipeBinding"
            contract="netBridge.Development.OfficeService.IWordService"
            bindingConfiguration="localBinding" /&gt;
  </code></pre>
  
  <p>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.</p>
  
  <ol>
  <li>Is this mex endpoint necessary for named pipes endpoint binding discovery?</li>
  <li>How should I add a service reference in the client app to the named pipe endpoint?</li>
  </ol>