OutWit.Communication.Client
2.0.0
See the version list below for details.
dotnet add package OutWit.Communication.Client --version 2.0.0
NuGet\Install-Package OutWit.Communication.Client -Version 2.0.0
<PackageReference Include="OutWit.Communication.Client" Version="2.0.0" />
<PackageVersion Include="OutWit.Communication.Client" Version="2.0.0" />
<PackageReference Include="OutWit.Communication.Client" />
paket add OutWit.Communication.Client --version 2.0.0
#r "nuget: OutWit.Communication.Client, 2.0.0"
#:package OutWit.Communication.Client@2.0.0
#addin nuget:?package=OutWit.Communication.Client&version=2.0.0
#tool nuget:?package=OutWit.Communication.Client&version=2.0.0
Base client logic for WitCom - OutWit.Communication - the easiest and most natural way to communicate with .Net processes/services/clients.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. 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 is compatible. 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 is compatible. 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. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net6.0
- OutWit.Communication (>= 2.0.0)
-
net7.0
- OutWit.Communication (>= 2.0.0)
-
net8.0
- OutWit.Communication (>= 2.0.0)
-
net9.0
- OutWit.Communication (>= 2.0.0)
NuGet packages (8)
Showing the top 5 NuGet packages that depend on OutWit.Communication.Client:
| Package | Downloads |
|---|---|
|
OutWit.Communication.Client.WebSocket
WebSocket transport client for WitRPC, enabling real-time, full-duplex communication over WebSocket connections (great for internet or browser-based clients). |
|
|
OutWit.Communication.Client.MMF
Memory-mapped file transport client for WitRPC, enabling high-speed inter-process communication via a shared memory region (for on-machine RPC calls). |
|
|
OutWit.Communication.Client.Pipes
Named Pipes transport client for WitRPC, allowing efficient inter-process communication via named pipes on the local machine (with support for multiple clients). |
|
|
OutWit.Communication.Client.Tcp
TCP transport client for WitRPC, enabling network communication over TCP sockets (with optional TLS support) to connect to WitRPC servers. |
|
|
OutWit.InterProcess.Host
Provides host-side functionality to launch external processes and connect to them via WitRPC, allowing your application to use out-of-process services as if they were local (handles process startup and client proxy generation). |
GitHub repositories
This package is not used by any popular GitHub repositories.