This project is read-only.

If You Need to Support WCF Clients on the Same Machine, Consider Using netNamedPipeBinding

- J.D. Meier, Carlos Farre, Jason Taylor, Prashant Bansode, Steve Gregersen, Madhu Sundararajan, Rob Boucher

If you need to support WCF clients on the same machine as your service, consider using the netNamedPipeBinding. Use this binding when you want to make use of the NamedPipe protocol and provide full support for SOAP security, transactions, and reliability.

The netNamedPipeBinding has the following characteristics:
  • It can only be consumed by WCF enabled clients.
  • Supports the WS* stack including reliable messaging, and secure transactions.
  • It only supports transport security; you cannot turn on message security.
  • The service can be hosted in IIS 5.0 or IIS 6.0, but it is not message activated, hence you can consider hosting in a Windows service or IIS 7.0 instead.
  • Your only authentication option is Windows.

The following example shows how to configure netNamedPipeBinding:
        <service behaviorConfiguration="" name="WCFServicecHost.MyService">
            <endpoint address="" binding="netNamedPipeBinding" bindingConfiguration=""
                name="namedPipeBinding" contract="WCFServicecHost.IMyService" />

Additional Resources

Last edited Jun 12, 2008 at 10:12 PM by prashantbansode, version 1


No comments yet.