NetCoreNamedPipeWrapper 1.0.0

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. 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.

<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
  <metadata>
    <id>NetCoreNamedPipeWrapper</id>
    <version>1.0.0</version>
    <authors>NamedPipeWrapper</authors>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <projectUrl>https://github.com/Joebu/named-pipe-wrapper</projectUrl>
    <description>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.

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.</description>
    <tags>namedpipe pipe .netcore</tags>
    <dependencies>
      <group targetFramework="net5.0">
        <dependency id="System.IO.Pipes.AccessControl" version="5.0.0" exclude="Build,Analyzers" />
      </group>
    </dependencies>
  </metadata>
</package>