locked
What version of IIS supports hosting netTcpBinding? RRS feed

  • Question

  • What version of IIS supports hosting netTcpBinding? I have to use Win XP Pro 64bit system and have IIS 6.0.

    Monday, November 9, 2009 4:59 PM

Answers

  • Greetings,

    You need to use IIS 7.0.

    The link is given below

    • http://www.iis.net/
    Internet Information Services (IIS) 7 Manager
    • http://blogs.msdn.com/carlosag/archive/2007/09/28/IIS7ManagerRC0ForWindowsXP_2D00_2003_2D00_Vista_2D00_SP1Available.aspx

    IIS Manager for Remote Administration

    • http://www.iis.net/extensions/IISManager
    Hope this helps you out

    Take Care

    PL - God Bless
    Helping People To Solve Technical Problems
    Monday, November 9, 2009 5:22 PM

All replies

  • NetTcpBinding Samples

    The samples in this section show how to use the NetTcpBinding binding.

    In This Section

    Default NetTcp Binding
    Demonstrates how to perform duplex communication over TCP.

    Net.TCP Port Sharing Sample
    Demonstrates how to enable the NetTcp Port Sharing feature.

    Related Sections

    Setup Instructions

    Basic Binding Samples

    Net Binding Samples

    The NetTcpBinding generates a run-time communication stack by default, which uses transport security, TCP for message delivery, and a binary message encoding. This binding is an appropriate Windows Communication Foundation (WCF) system-provided choice for communicating over an Intranet.

    The default configuration for the NetTcpBinding is faster than the configuration provided by the WSHttpBinding, but it is intended only for WCF-to-WCF communication. The security behavior is configurable using the optional securityMode parameter in the constructor. The use of WS-ReliableMessaging is configurable using the optional reliableSessionEnabled parameter. But reliable messaging is off by default. More generally, the HTTP system-provided bindings such as WSHttpBinding and BasicHttpBinding are configured to turn things on by default, whereas the NetTcpBinding binding turns things off by default so that you have to opt-in to get support, for example, for one of the WS-* specifications. This means that the default configuration for TCP is faster at exchanging messages between endpoints than that configured for the HTTP bindings by default.


    http://msdn.microsoft.com/en-us/library/system.servicemodel.nettcpbinding.aspx
    Monday, November 9, 2009 5:13 PM
  • Greetings,

    You need to use IIS 7.0.

    The link is given below

    • http://www.iis.net/
    Internet Information Services (IIS) 7 Manager
    • http://blogs.msdn.com/carlosag/archive/2007/09/28/IIS7ManagerRC0ForWindowsXP_2D00_2003_2D00_Vista_2D00_SP1Available.aspx

    IIS Manager for Remote Administration

    • http://www.iis.net/extensions/IISManager
    Hope this helps you out

    Take Care

    PL - God Bless
    Helping People To Solve Technical Problems
    Monday, November 9, 2009 5:22 PM
  • You need to enable WAS on IIS 7.x

    http://msdn.microsoft.com/en-us/library/ms730158.aspx
    http://msdn.microsoft.com/en-us/library/ms731053.aspx
    http://msdn.microsoft.com/en-us/library/ms733109.aspx

    But it only works on IIS7 (Vista, Windows 7 and Win2008). I don't think it's possible to install IIS7 on WinXP. In your development machine you could think to host in a Windows Service .

    HTH
    Fabio Cozzolino Blogs: http://dotnetside.org/blogs/fabio http://weblogs.asp.net/fabio
    Monday, November 9, 2009 5:28 PM
  • I believe we will revert back to just using wsHttpbinding because of the restrictions in wsDualHttpbinding and netTcpBinding. 

    I have another question? How do I track a list of clients connected to the WCF Service similar to wsDualHttpBinding and netTcpbinding?
    For example, the wcf service can use

                    IServicesCallback callBack = OperationContext.Current.GetCallbackChannel<IServicesCallback>();
    
    and keep a list of clients connected. That way the wcf service can determine which client is calling.
    Monday, November 9, 2009 6:01 PM
  • Hi Johny,

    For those non-dual bindings, it would be a bit hard to track the client connections from service code level. Are you using teh reliableSession for the binding your service used? 

    If the binding is reliableSession enabled, you can consider using SessionId (from OperationContext) identify the certain client-server session channel:

    ===========
     OperationContext.Current.SessionId
    ===========

    #Reliable Sessions Overview
    http://msdn.microsoft.com/en-us/library/ms733136.aspx


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Monday, November 16, 2009 5:51 AM
  • IIS 7.0 is needed.
    Tuesday, May 15, 2012 1:12 PM