NamedPipeWrapper.New 1.5.0-beta1

.NET Framework 4.0 This package targets .NET Framework 4.0. The package is compatible with this framework or higher.
This is a prerelease version of NamedPipeWrapper.New.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package NamedPipeWrapper.New --version 1.5.0-beta1                

                    
                

            
NuGet\Install-Package NamedPipeWrapper.New -Version 1.5.0-beta1
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="NamedPipeWrapper.New" Version="1.5.0-beta1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add NamedPipeWrapper.New --version 1.5.0-beta1                

                    
                

            
#r "nuget: NamedPipeWrapper.New, 1.5.0-beta1"
#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 NamedPipeWrapper.New as a Cake Addin
#addin nuget:?package=NamedPipeWrapper.New&version=1.5.0-beta1&prerelease

// Install NamedPipeWrapper.New as a Cake Tool
#tool nuget:?package=NamedPipeWrapper.New&version=1.5.0-beta1&prerelease

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.

Product Compatible and additional computed target framework versions.
.NET Framework net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.5.1-beta2 994 4/1/2016
1.5.0-beta1 750 4/1/2016

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.