dotnet-serialization

To make JSON serialization work with .NET Native AOT, use System.Text.Json source generators to generate serialization code at compile-time. This avoids reflection at runtime, ensuring your AOT and trimming scenarios remain compatible and performant.

The best way to migrate from Newtonsoft.Json to an AOT-compatible serializer is adopting System.Text.Json source generators, Protobuf, or MessagePack. These approaches eliminate reflection-based dependencies, enabling efficient data exchange while avoiding runtime errors in Native AOT environments.

Protobuf and MessagePack both offer AOT-compatible serialization for .NET, but performance depends on payload size and structure. Protobuf is ideal for compact binary data exchange, while MessagePack provides fast binary serialization, with tradeoffs in payload efficiency compared to JSON.

Reflection-based serialization breaks in trimmed .NET MAUI applications because the trimming compiler removes metadata and type information that reflection relies on at runtime. Switching to System.Text.Json source generators, Protobuf, or MessagePack resolves this by shifting serialization logic to compile-time.

Yes, you can use System.Text.Json source generators for compile-time serialization in C#. They generate type-specific serialization code during the build process, removing the need for runtime reflection and ensuring your .NET applications remain AOT-friendly and trim-safe.