Named pipes are one of the fastest ways to make IPC (interprocess communication) on a single computer. They existed for a long time (was NT4 the first OS?) And are not specific to WCF.
I would, however, not use WCF / Named pipe through ASP.NET, since IIS does not use named pipes for communication. this means that your application will close if IIS has not received HTTP requests for a while.
How you should host your IPC depends on the type of application. If you want your server to always work, you must host it on a Windows service. Otherwise, you can simply include it in your desktop application.
You donβt have to use WCF, you can directly use named pipes (look at the link at the beginning of my post). It all depends on how complicated your communication is.
source share