H.Formatters.BinaryFormatter 2.0.30

There is a newer version of this package available.
See the version list below for details.
dotnet add package H.Formatters.BinaryFormatter --version 2.0.30
NuGet\Install-Package H.Formatters.BinaryFormatter -Version 2.0.30
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="H.Formatters.BinaryFormatter" Version="2.0.30" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add H.Formatters.BinaryFormatter --version 2.0.30
#r "nuget: H.Formatters.BinaryFormatter, 2.0.30"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install H.Formatters.BinaryFormatter as a Cake Addin
#addin nuget:?package=H.Formatters.BinaryFormatter&version=2.0.30

// Install H.Formatters.BinaryFormatter as a Cake Tool
#tool nuget:?package=H.Formatters.BinaryFormatter&version=2.0.30

Async Named Pipe Wrapper for .NET Standard 2.0

Language License Requirements Build Status

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 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.Newtonsoft.Json, H.Formatters.System.Text.Json and H.Formatters.Ceras
  • Supports PipeAccessRule's(see H.Pipes.AccessControl nuget package) or more complex code to access using the PipeServer.PipeStreamInitializeAction property

Nuget

NuGet NuGet NuGet NuGet NuGet

// All clients and servers that do not need support AccessControl.
Install-Package H.Pipes

// Servers that need support AccessControl.
Install-Package H.Pipes.AccessControl

// If you want to transfer any data that can be serialized/deserialized in json using Newtonsoft.Json.
Install-Package H.Formatters.Newtonsoft.Json

// If you want to transfer any data that can be serialized/deserialized in json using System.Text.Json.
Install-Package H.Formatters.System.Text.Json

// If you want to transfer any data that can be serialized/deserialized in binary using Ceras.
Install-Package H.Formatters.Ceras

Usage

Server:

await using var server = new PipeServer<MyMessage>(pipeName);
server.ClientConnected += async (o, args) =>
{
    Console.WriteLine($"Client {args.Connection.PipeName} is now connected!");

    await args.Connection.WriteAsync(new MyMessage
    {
        Text = "Welcome!"
    });
};
server.ClientDisconnected += (o, args) =>
{
    Console.WriteLine($"Client {args.Connection.PipeName} disconnected");
};
server.MessageReceived += (sender, args) =>
{
    Console.WriteLine($"Client {args.Connection.PipeName} says: {args.Message}");
};
server.ExceptionOccurred += (o, args) => OnExceptionOccurred(args.Exception);

await server.StartAsync();

await Task.Delay(Timeout.InfiniteTimeSpan);

Client:

await using var client = new PipeClient<MyMessage>(pipeName);
client.MessageReceived += (o, args) => Console.WriteLine("MessageReceived: " + args.Message);
client.Disconnected += (o, args) => Console.WriteLine("Disconnected from server");
client.Connected += (o, args) => Console.WriteLine("Connected to server");
client.ExceptionOccurred += (o, args) => OnExceptionOccurred(args.Exception);

await client.ConnectAsync();

await client.WriteAsync(new MyMessage
{
    Text = "Hello!",
});

await Task.Delay(Timeout.InfiniteTimeSpan);

Notes:

  • To use the server inside the WinForms/WPF/Other UI application, use Task.Run() or any alternative.
  • Be careful and call Dispose 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

Install-Package H.Formatters.Newtonsoft.Json
Install-Package H.Formatters.System.Text.Json
Install-Package H.Formatters.Ceras
using H.Formatters;

await using var server = new PipeServer<MyMessage>(pipeName, formatter: new NewtonsoftJsonFormatter());
await using var client = new PipeClient<MyMessage>(pipeName, formatter: new NewtonsoftJsonFormatter());

Access Control

Install-Package H.Pipes.AccessControl
using System.IO.Pipes;
using H.Pipes.AccessControl;

await using var server = new PipeServer<string>(pipeName);

// You can set PipeSecurity
var pipeSecurity = new PipeSecurity();
pipeSecurity.AddAccessRule(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.BuiltinUsersSid, null), PipeAccessRights.ReadWrite, AccessControlType.Allow));

server.SetPipeSecurity(pipeSecurity);

// or just add AccessRule's (Please be careful, the server will only consider AccessRules from the last call AddAccessRules())
server.AddAccessRules(new PipeAccessRule(new SecurityIdentifier(WellKnownSidType.BuiltinUsersSid, null), PipeAccessRights.ReadWrite, AccessControlType.Allow));

// or just
server.AllowUsersReadWrite();

Encryption

Install-Package H.Formatters.Inferno
using H.Formatters;

await using var server = new PipeServer<MyMessage>(pipeName, formatter: new SystemTextJsonFormatter());
server.EnableEncryption();

await using var client = new PipeClient<MyMessage>(pipeName, formatter: new SystemTextJsonFormatter());
client.EnableEncryption();

await client.ConnectAsync(source.Token).ConfigureAwait(false);
// Waits for key exchange.
await client.Connection!.WaitExchangeAsync();

server.ClientConnected += async (_, args) =>
{
    // Waits for key exchange.
    await args.Connection.WaitExchangeAsync();

    await args.Connection.WriteAsync(new MyMessage
    {
        Text = "Welcome!"
    }, source.Token).ConfigureAwait(false);
};

GetImpersonationUserName

server.ClientConnected += async (o, args) =>
{
    var name = args.Connection.GetImpersonationUserName();

    Console.WriteLine($"Client {name} is now connected!");
};

Inter-process communication

I recommend that you take a look at my other library if you plan on doing IPC. It is based on this library, but provides an IPC implementation based on C# interfaces. It supports remote method invocation, asynchronous methods, cancellation via CancellationToken, events, and so on.

Contacts

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net451 is compatible.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on H.Formatters.BinaryFormatter:

Package Downloads
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

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.1.0-dev.322 84 1/20/2024
2.1.0-dev.318 126 12/18/2023
2.0.59 12,130 12/8/2023
2.0.56 1,579 11/27/2023
2.0.53 18,318 7/24/2023
2.0.51 9,851 5/25/2023
2.0.47 15,477 2/27/2023
2.0.46 966 2/26/2023
2.0.45 6,081 2/2/2023
2.0.44 8,389 1/10/2023
2.0.43 1,911 1/5/2023
2.0.42 23,407 9/14/2022
2.0.41 2,027 9/9/2022
2.0.40 3,170 8/26/2022
2.0.39 1,529 8/26/2022
2.0.38 11,298 6/2/2022
2.0.37 3,921 4/21/2022
2.0.35 50,674 3/17/2022
2.0.34 1,735 3/12/2022
2.0.33 1,607 3/12/2022
2.0.32 1,582 3/12/2022
2.0.31 2,440 3/11/2022
2.0.30 1,592 3/11/2022
2.0.29 1,645 3/11/2022
2.0.26 1,689 3/7/2022
2.0.25 1,580 3/6/2022
2.0.23 9,000 12/21/2021
2.0.22 978 12/21/2021
2.0.21 2,288 12/20/2021
2.0.20 1,013 12/20/2021
2.0.19 1,035 12/20/2021
2.0.18 1,045 12/20/2021
2.0.17 1,022 12/20/2021
2.0.16 942 12/20/2021
1.0.0.8 8,885 11/25/2021
1.0.0.7 7,797 11/24/2021
1.0.0.6 12,540 1/4/2021
1.0.0.5 12,268 12/9/2020
1.0.0.4 1,083 12/9/2020
1.0.0.3 4,925 11/22/2020
1.0.0.2 3,986 8/4/2020
1.0.0.1 8,721 1/28/2020
1.0.0 5,172 1/10/2020

⭐ Last 10 features:
- feat(AccessControl): Added explicit net5.0 and net6.0 target frameworks. 2022-03-11
- feat: Excluded WaitForPipeDrain call for non-windows platforms. 2022-03-11
- feat: Added SystemTextJsonFormatter.Options property. 2022-03-06
- feat: Added connection close if EnableEncryption fails. 2021-12-21
- feat: Added WaitExchangeAsync use example. 2021-12-20
- feat: Added Inferno PipeConnectionExtensions.WaitExchangeAsync extension. 2021-12-20
- feat: IPipeClient Connection/PipeName/ServerName now public properties. 2021-12-20
- feat: Updated README. 2021-12-20
- feat: Added ContinuousIntegrationBuild. 2021-12-20
- feat: Updated Microsoft.SourceLink.GitHub to 1.1.1. 2021-12-20

🐞 Last 10 bug fixes:
- fix(AccessControl): Fixed NET461 library to use Net Framework NamedPipeServerStream ctor. 2022-03-11
- fix: Fixed ValidatePublicKey. 2022-03-07
- fix: Fixed PipeClient.Connection set access. 2021-12-21
- fix: Fixed problem with multiple server encrypted connections. 2021-12-20
- fix: Fixed EnableEncryption client/server settings. 2021-12-20
- fix: Fixed Inferno KeyPair missing disposing. 2021-12-20
- fix: Fixed some Inferno KeyPair code. 2021-12-20
- fix: Converted Inferno KeyPair to internal class. 2021-12-20
- fix: Fixed Inferno namespaces. 2021-12-20
- fix: Fixed Inferno extensions memory leak. 2021-12-20