Simply one of the fastest and most robust inter-process communcations available
on the Windows platform. WinRPC is the building block of DCOM and probably the
most used remote proceedure call in Windows. In plain words it is the fastest,
most stable, secure transport available. Use it for authenticated or anonymous
communications over LRPC, named-pipes, or tcp/ip.
This assembly provides all the interop nessessary to start a server or client;
however, it is a transport only implementation. In other words, it provides no
more than moving a byte back and forth with the remote endpoint. A protocol
is usually layered on top of this to turn raw bytes into meaningful messages.
See the version list below for details.
Install-Package CSharpTest.Net.RpcLibrary -Version 1.11.924.348
dotnet add package CSharpTest.Net.RpcLibrary --version 1.11.924.348
<PackageReference Include="CSharpTest.Net.RpcLibrary" Version="1.11.924.348" />
paket add CSharpTest.Net.RpcLibrary --version 1.11.924.348
#r "nuget: CSharpTest.Net.RpcLibrary, 1.11.924.348"
This package has no dependencies.
NuGet packages (3)
Showing the top 3 NuGet packages that depend on CSharpTest.Net.RpcLibrary:
A library containing classes to use propertysheets with MsBuild scripts. [Note: This library is not quite ready for public consumption--I'm in the middle of some code reorganization]
Google.ProtocolBuffers.Rpc uses the Win32 RPC Interop library, CSharpTest.Net.RpcLibrary, as a primary transport for Protobuffer services. Extremely fast, secure, extensible, and reliable.
Google.ProtocolBuffersLite.Rpc uses the Win32 RPC Interop library, CSharpTest.Net.RpcLibrary, as a primary transport for Protobuffer services. Extremely fast, secure, extensible, and reliable. This version depends on Google.ProtocolBuffersLite version (optimize_for = LITE_RUNTIME).
This package is not used by any popular GitHub repositories.