Named pipe wrappers to simplify named-pipe use in your application. PipeClient for clients and PipeServer for single-instance servers. As pipes must have a server for each connected client, PipeHost will host multple PipeServers with the same pipe name.
See the version list below for details.
Install-Package Tungsten.IO.Pipes -Version 2.0.1
dotnet add package Tungsten.IO.Pipes --version 2.0.1
<PackageReference Include="Tungsten.IO.Pipes" Version="2.0.1" />
paket add Tungsten.IO.Pipes --version 2.0.1
I yield. Pipes just can't be forced to do what they weren't designed to do. W.IO.Pipes has been refactored to be like traffic on a one-way bridge. Use PipeClient and PipeHost in most scenarios. There is a PipeServer which can be used for single instance servers (or if you want to write your own host).
This package is not used by any popular GitHub repositories.