SetNet.Json 1.1.0

dotnet add package SetNet.Json --version 1.1.0
                    
NuGet\Install-Package SetNet.Json -Version 1.1.0
                    
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="SetNet.Json" Version="1.1.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="SetNet.Json" Version="1.1.0" />
                    
Directory.Packages.props
<PackageReference Include="SetNet.Json" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add SetNet.Json --version 1.1.0
                    
#r "nuget: SetNet.Json, 1.1.0"
                    
#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.
#:package SetNet.Json@1.1.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=SetNet.Json&version=1.1.0
                    
Install as a Cake Addin
#tool nuget:?package=SetNet.Json&version=1.1.0
                    
Install as a Cake Tool

<p align="center"> <img src="https://raw.githubusercontent.com/Povstalez/SetNet/master/assets/icon.png" alt="SetNet" width="96"> </p>

SetNet.Json

System.Text.Json serializer for SetNet.

SetNet ships no serializer in the core — you register one at startup. This package plugs in System.Text.Json, giving you human-readable, self-describing payloads. Reach for it when you want to eyeball traffic while debugging, interop with a browser / non-.NET JSON client, or avoid annotating your DTOs at all. The trade-off is size and speed: JSON is larger on the wire and slower to (de)serialize than a binary format like MessagePack or MemoryPack — for chatty realtime traffic prefer one of those (optionally behind SetNet.Compression).

Install

dotnet add package SetNet
dotnet add package SetNet.Json

Usage

Register the serializer once at startup, before you create any client or server. Both ends of a connection must use the same serializer.

using SetNet.Json;
using SetNet.Messaging;

SetNetSerializer.Use(new JsonNetSerializer());

Your message types are plain POCOs — no attributes required:

public class ChatMessage
{
    public string User { get; set; } = "";
    public string Text { get; set; } = "";
}

Need custom converters, camelCase naming, enums-as-strings, etc.? Pass your own JsonSerializerOptions:

var options = new JsonSerializerOptions
{
    PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
    Converters = { new JsonStringEnumConverter() }
};

SetNetSerializer.Use(new JsonNetSerializer(options));

Under the hood, Serialize<T> uses JsonSerializer.SerializeToUtf8Bytes and Deserialize<T> uses JsonSerializer.Deserialize<T>, both with your options.

Notes

  • Payload size: JSON is text; property names ship with every message. Expect noticeably larger frames than MessagePack/MemoryPack/Protobuf. If size matters, wrap it with SetNet.Compression — text-like JSON compresses very well.
  • Speed: System.Text.Json is fast for a text format, but binary source-generated serializers are faster and allocate less.
  • AOT / IL2CPP (Unity): reflection-based System.Text.Json can be fragile under aggressive trimming/AOT. For Unity/IL2CPP prefer SetNet.MemoryPack (source-generated, no runtime reflection), or wire up System.Text.Json source generation yourself.
  • Interop: any client that can produce/consume the same JSON shape can talk to a SetNet endpoint using this serializer — but both ends must agree on the exact JSON contract.
  • Depends on System.Text.Json (8.0.5).

Documentation & source

License

MIT

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  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 was computed.  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 was computed.  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 was computed.  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. 
.NET Core netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.1 is compatible. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.1.0 133 7/2/2026