H.Pipes
Features: - 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. - Async - Requires .NET Standard 2.0 - Supports large messages - up to 300 MiB. - Server restart automatically - Automatically wait for the release of the pipe for the server, if it is already in use - Automatically waiting for a server pipe creating when client connecting - Automatic reconnect with a given interval and at each `client.WriteAsync`, if necessary - Supports variable formatters, default - BinaryFormatter which uses System.Runtime.Serialization.BinaryFormatter inside - Also available ready formatters in separate nuget packages: H.Formatters.Json - Supports `PipeAccessRule`'s(see `H.Pipes.AccessControl` nuget package) or more complex code to access using the `PipeServer.PipeStreamInitializeAction` property
Install
dotnet add package H.Pipes --version 2.1.0-dev.318
Install-Package H.Pipes -Version 2.1.0-dev.318
<PackageReference Include="H.Pipes" Version="2.1.0-dev.318" />
Frameworks
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
This version is marked prerelease. Validate its API and upgrade path before production use.
Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.