OutWit.Communication.Server
2.0.0
See the version list below for details.
dotnet add package OutWit.Communication.Server --version 2.0.0
NuGet\Install-Package OutWit.Communication.Server -Version 2.0.0
<PackageReference Include="OutWit.Communication.Server" Version="2.0.0" />
<PackageVersion Include="OutWit.Communication.Server" Version="2.0.0" />
<PackageReference Include="OutWit.Communication.Server" />
paket add OutWit.Communication.Server --version 2.0.0
#r "nuget: OutWit.Communication.Server, 2.0.0"
#:package OutWit.Communication.Server@2.0.0
#addin nuget:?package=OutWit.Communication.Server&version=2.0.0
#tool nuget:?package=OutWit.Communication.Server&version=2.0.0
Base server 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.Server:
| Package | Downloads |
|---|---|
|
OutWit.Communication.Server.Pipes
Named Pipes transport server for WitRPC, enabling a server to handle client connections over named pipes (efficient local IPC with support for multiple clients). |
|
|
OutWit.Communication.Server.WebSocket
WebSocket transport server for WitRPC, enabling a server to accept clients over WebSocket (great for real-time, browser-friendly communication). |
|
|
OutWit.Communication.Server.MMF
Memory-mapped file transport server for WitRPC, allowing a server to listen for client connections via a shared memory segment (for high-performance on-machine communication). |
|
|
OutWit.Communication.Server.Rest
REST transport server for WitRPC, exposing your services as HTTP REST endpoints to allow calls from web or external clients via standard HTTP. |
|
|
OutWit.Communication.Server.Tcp
TCP transport server for WitRPC, enabling a server to host services over a TCP port (supports plaintext or TLS-secured connections). |
GitHub repositories
This package is not used by any popular GitHub repositories.