(winXP) The protocol 'net.tcp' is not supported error while debugging

Question

I'm trying to test a nettcp service in debug mode but whenever I launch it and try to load it in a browser I get the error:

The protocol 'net.tcp' is not supported.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The protocol 'net.tcp' is not supported.


I understand that netTCP can only be hosted in IIS7 and thats fine as thats where it will be going but I'd like to at least be able to debug on my home XP machine. Is that possible?



Web Config:
...

      <service name="Warden.Service.Priv.Bugle">
        <endpoint address="net.tcp://localhost" binding="netTcpBinding" bindingConfiguration="BugleBinding" contract="Warden.Service.Priv.IBugle" />
      </service>

...

      <netTcpBinding>
        <binding name="BugleBinding">
          <security mode="None"/>
        </binding>
      </netTcpBinding>

...



Thanks in advance for the help.
-Josh

Answer 1

Hi Josh,

you can't use the netTcpBinding when hosting your service under the IIS 5.1, only http bindings are allowed. You can host your service in a simple console application or use the WcfSvcHost helper app and port it to IIS 7 later on.

Regards,
John

Answer 2

sorry to bring up this thread from the past, but i'm desperately trying to have Visual Studio 2008 auto-generate a proxy for a WCF service using netTcpBindin. as the proxy generation tool in VS2k8 uses the ASP.NET development server, this, of course, fails with "The protocol 'net.tcp' is not supported".

any ideas on how to auto-generate the proxy with VS2k8?

thanks,
Tom

Answer 3

answered the problem myself. just in case someone else encounters this problem:
instead of trying to create the proxy via the "Discover --> Services in Solution"  in the "Add Service Reference" dialog, which seems to launch the ASP.NET development server, just compile your service + some hosting application (or run it as a service), and launch it. now that it's running, just create a service reference by manually entering its address and hit Go. This works for me without using that crappy ASP.NET Dev Server.