Search code examples
wcfiiswindows-server-2008wcf-binding

Benefits & pitfalls of moving to IIS 7, Windows Server 2008 for WCF Services


We're currently using IIS 6 and Windows Server 2003 for our web and application servers. Our web servers make WCF Service calls to our application servers.

We'd like to move to IIS 7 and Windows Server 2008 so that we can use the recommended netTcpBinding (at the moment we're using a basicHttpBinding).

(along with this we'd also move from SQL Server 2005 to 2008)

Does anyone have any points to make about the benefits and pitfalls of the above?


Solution

  • As you mentioned, IIS 6 only has support for the various HTTP-based bindings. IIS7 has support for all the bindings, including TCP/IP, named pipes (for superfast in-proc calls on the same machine), and MSMQ queue.

    For a detailed comparison between hosting WCF in IIS6 and IIS7, see this MSDN article: Extend Your WCF Services Beyond HTTP With WAS