As far as I know, NetTcpBinding can only be used for WCF to WCF communication. Since this binding does use several of
WS-* protocols, I'm a bit puzzled why it can't also be used to for communication with non-WCF clients??
The protocols used in the message are WS-* protocols, but how the message is encoded (the XML infoset, the framing used in the TCP communication, some dictionaries used to compress the message) are not.
The protocols used in the message are WS-* protocols, but how the message is encoded (the XML infoset, the framing used in the TCP communication, some dictionaries used to compress the message) are not.