HavenDV / H.Pipes
A simple, easy to use, strongly-typed, async wrapper around .NET named pipes.
View on GitHubAI Architecture Analysis
This repository is indexed by RepoMind. By analyzing HavenDV/H.Pipes in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewAsync Named Pipe Wrapper for .NET Standard 2.0 A simple, easy to use, strongly-typed, async wrapper around .NET named 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 , if necessary • Supports variable formatters, default - BinaryFormatter which uses System.Runtime.Serialization.BinaryFormatter inside • Also available ready formatters in separate nuget packages: H.Formatters.Newtonsoft.Json, H.Formatters.System.Text.Json and H.Formatters.Ceras • Supports 's(see nuget package) or more complex code to access using the property • Supports Trimming/NativeAOT Nuget Usage Server: Client: Notes: • To use the server inside the WinForms/WPF/Other UI application, use Task.Run() or any alternative. • Be careful and call before closing the program/after the end of use. Pipes are system resources and you might have problems restarting the server if you don't properly clean up the resources. Custom Formatters Since BinaryFormatter is used by default, you should check out this article: https://docs.microsoft.com/en-us/dotnet/standard/serialization/binaryformatter-security-guide Access Control > [!WARNING] > this is only available for the Windows platform. Encryption > [!WARNING] > this is only available for the Windows platform. GetImpersonationUserName Inter-process communication I recommend that you take a look at my other library if you plan on doing IPC. This is a SourceGenerator that will generate client and server code based on the presented interface. Contacts • mail