Create named pipe servers that can handle multiple client connections simultaneously.
Send strongly-typed messages between clients and servers: any serializable .NET object can be sent over a pipe and will be automatically serialized/deserialized, including cyclical references and complex object graphs.
Messages are sent and received asynchronously on a separate background thread and marshalled back to the calling thread (typically the UI).
Supports large messages - up to 300 MiB.
Requires .NET 4.0 full.
The package was forked from NamedPipeWrapper 1.4.0 creadted by Andrew C. Dvorak and the original project url is https://github.com/acdvorak/named-pipe-wrapper.
See the version list below for details.
Install-Package NamedPipeWrapper.New -Version 1.5.0-beta1
dotnet add package NamedPipeWrapper.New --version 1.5.0-beta1
<PackageReference Include="NamedPipeWrapper.New" Version="1.5.0-beta1" />
paket add NamedPipeWrapper.New --version 1.5.0-beta1
1.Solved the problem of NamedPipeWrapper 1.4.0 that a program tries to call the Start() method of a NamedPipeServer instance when there is NamedPipeServer instance with the same pipe name started on the same computer, the thread started by the Start() method will throw a IOException will cannot be caught. To avoid this, I added a mutex to the Server<TRead, TWrite> class(the base class of NamedPipeServer) and let Server<TRead, TWrite>.Start() return false if here is NamedPipeServer instance with the same pipe name started on the same computer.
2.Lets the Server<TRead, TWrite> implement the IDispoable interface to release the pipe name mutex and call Close() when being disposed.
3.Adds a readonly PipeName property to NamedPipeServer and NamedPipeClient for convenience.
This package has no dependencies.
This package is not used by any NuGet packages.
This package is not used by any popular GitHub repositories.