WCF Using net.tcp binding

Question

I'm running Windows 7 64-bit. I'm attempting to host a WCF service which will use Windows security (net.tcp binding) on IIS7. The service I'm running is a very simple skeleton app, which works fine so far with HTTP and HTTPS. (I've finally gotten HTTPS to work and I'm just trying to add another binding--NET.TCP.)

I've configured IIS to enable net.tcp: I added a net.tcp binding with Binding information "808:*". My "Advanced Settings -> Enabled Protocols" field is set to "https,net.tcp".

The entire solution (contains the service application and a client app which consumes both http and https) can be found at http://petio.org/2011/06/29/MagicEightBall.zip. In the service Web.config, a copy of which can be found at http://petio.org/2011/06/29/MagicEightBall/Web.config,

I have three endpoints: http, https, and net.tcp. Right now http and https are working properly, but I have the net.tcp endpoint commented out. When I uncomment this, it breaks http and https, and then when I navigate to http://localhost/MagicEightBall/MagicEightBallService.svc, I see the error:

The protocol 'net.tcp' is not supported.

What am I doing wrong? All code is posted on the above links, or you can navigate the solution via ftp://petio.org/2011/06/29/MagicEightBall/.

By the way, I've already activated 'Windows Communication Foundation Non-HTTP Activation', and made sure the 'Net.Tcp Listener Adapter' service is running.

Any help is greatly appreciated.

Thanks,

Jay Sullivan

Answer 1

Most likely an IIS issue - it's a bit tricky and unintuitive to get to work at first.

Read:

• Configuring Internet Information Services 7.0 for Windows Communication Foundation

and then:

• How to: Install and Configure WCF Activation Components

Those steps are needed - if you do them correctly and in the right order, everything should work fine after that.