When I expose a service using NetTcpBinding, is .Net remoting used under the surface? Could I consume this service using .Net remoting on the client side?
I ask this because I always thought that WCF was just a wrapper for underlying protocols such as WS*, Remoting, COM+, and MSMQ. And while I know that exposing WS* will work as expected, the others seem to be more ambivalent.
WCF is more than "just" a wrapper. It's a pseudo-magic layer that handles a ton of stuff for component developers according to configuration information. With WCF you can create a service contract and an implementation and then use them across multiple machines via HTTP, HTTPS, NET-TCP, on a single machine via named pipes, securely, non-securely, etc etc all just by adjusting configuration settings.
This is way, way different from what .net remoting does.
Grab a copy of "Programming WCF Services" by Juval Lowy to get a better feeling for what all you can do with WCF.