This project is read-only.

If you are coming from DCOM then, use netTcpBinding.

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

If you are coming from DCOM the equivalent on WCF is using the netTcpBinding. WCF Service using netTcpBinding needs to be hosted in a Windows service unless your are using IIS 7.0 or later version. The netTcpBinding uses the TCP protocol and provides full support for SOAP security, transactions, and reliability. Use this binding when you want to provide a secure and reliable binding environment for .NET-to-.NET cross-machine communication.

The netTcpBinding has the following characteristics:
  • It can only be consumed by WCF enabled clients.
  • Supports the WS* stack including reliable messaging, message security, and secure transactions.
  • Transport security is turned on by default, message security is also available.
  • The service cannot be hosted in IIS 6.0, you can host in a Windows service instead.
  • If you choose to use message security you can use certificates, username, Windows or token authentication
  • If you choose to use transport security you can only use certificates or Windows authentication

The following example shows a netTcpBinding configuration section:
         <binding name = “myNetTcpBinding”>

Last edited Apr 24, 2008 at 12:03 AM by prashantbansode, version 1


ronjacobs May 19, 2008 at 2:35 AM 
The service can be hosted with WAS in IIS 7 with TCP activation enabled.