Use Json.NET instead of Newtonsoft.Json

[molnard]

From .NET Core 3 MS started to implement its own JSON library. It would be better to use that sooner or later. Apparently it is not ready to overtake Newtonsoft place, there are incompatibilities and missing implementations but it is good to keep an eye on it.

First, try to replace is here:
#2573

[MaxHillebrand]

what's up with this?

[molnard]

There are many unsupported features still in Json.NET, here is a comparison

https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to?pivots=dotnet-6-0

[kiminuo]

Update: https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/migrate-from-newtonsoft?pivots=dotnet-8-0#table-of-differences

I'm not sure what features we really want. AFAIK we can use STJ and enjoy its better performance and lower memory footprint. Also STJ has code generators support so it avoids reflection.

A minor step forward would be to say: Do not introduce new Newtonsoft.JSON code. (when there is a choice)

Examples of people porting to STJ

• Switch Roslyn protocol types to System.Text.Json serialization dotnet/roslyn#73207

[molnard]

I put this on the RR board for evaluation.