What is the best choice for .NET inter-process communication? [closed]

c# .net process ipc

Should I use Named Pipes, or .NET Remoting to communicate with a running process on my machine?


WCF is the best choice. It supports a number of different transport mechanisms (including Named Pipes) and can be completely configuration driven. I would highly recommend that you take a look at WCF.

Here is a blog that does a WCF vs Remoting performance comparison.

A quote from the blog:

The WCF and .NET Remoting are really comparable in performance. The differences are so small (measuring client latency) that it does not matter which one is a bit faster. WCF though has much better server throughput than .NET Remoting. If I would start completely new project I would chose the WCF. Anyway the WCF does much more than Remoting and for all those features I love it.

MSDN Section for WCF


If it's on a single machine, Named Pipes gives you better performance and can be implemented with the remoting infrastructure as well as WCF. Or you can just directly use System.IO.Pipes.

Related

How to parse JSON Array (Not Json Object) in Android
Uncaught ReferenceError: function is not defined with onclick
Benefits of using the conditional ?: (ternary) operator
Array initialization syntax when not in a declaration
When to use and when not to use Python 3.5 `await` ?
Subclass/inherit standard containers?
How do I escape special characters in MySQL?
Property [title] does not exist on this collection instance
What is the size of an enum in C?
Values of disabled inputs will not be submitted
Including jars in classpath on commandline (javac or apt)
Committing Machine Specific Configuration Files