Using NetNamedPipe on a network?

We are building a window service that starts/stops other processes, and the communication between the UI and the service is with NetNamedPipe.

Every process have a host that can get shutdown call (st开发者_如何学编程ill with NetNamedPipe in order to avoid port cross).

I have used it on my computer and when I moved it to the server it didn't work (NetNamedPipe is not for cross network - now I know).

Is there any way to do this right?

If this is going to run on the local network, I would suggest using a TCP endpoint on your WCF service to connect to instead of the Named Pipe endpoint.

For .Net - to - .Net communication, it's best to use NetTcp. You would use Http when mixing technologies (.Net to COM / Java, for instance), or when a firewall would otherwise block your communication.

So Http is what you use only if there are reasons not to use NetTcp.