Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Move library from Newtonsoft.Json to System.Text.Json

See original GitHub issue

Microsoft & many developers have been moving their apps & libraries from Newtsoft.Json to System.Text.Json recently (e.g. the Microsoft Graph SDK for .NET). It would be very appreciated if this library could be moved as well. Not only is System.Text.Json faster and more efficient, it is also already used by many developers and libraries. Newtonsoft.Json isn’t exactly the smallest .dll and increases the binaries of apps we are creating with the Google API Library for .NET.

This suggestion has been posted by @LindaLawton in https://github.com/googleapis/google-api-dotnet-client/issues/1464#issuecomment-945831437 before and I have read the discussion following on it but I was afraid that this doesn’t get the visibility needed when not posted as an own feature request.

Issue Analytics

State:
Created 2 years ago
Reactions:8
Comments:16

Top GitHub Comments

6reactions

tipacommented, May 6, 2022

.NET Framework 4.6.1 (among others) has reached end-of-support now so that’s one obstacle less 😃 Would love to see System.Text.Json to be used at some point in the future

1reaction

jskeetcommented, Nov 18, 2021

@guillaume86: Please could you file a new issue with the details of what you’re trying to achieve, and why it needs new attributes to be applied? It sounds like it’s a somewhat different use case than “Please migrate off Newtonsoft.Json” in this case. (Can your serialization not just use the default property names?) There’s some potential there, although we wouldn’t target .NET 5 as it’s not an LTS - we’d make it .NET 6.0+, if we do it at all. To set expectations, I doubt that we’ll be able to put much time into even considering this until Q1 of 2022.

Top Results From Across the Web

Migrate from Newtonsoft.Json to System.Text.Json - .NET

Learn about the differences between Newtonsoft.Json and System.Text.Json and how to migrate to System.Text.Json.

Migrate from Newtonsoft.Json to System.Text.Json - .NET

Text.Json. This article shows how to migrate from Newtonsoft.Json to xref:System.Text. ... The System.Text.Json library is included in the runtime for .

Migrating Newtonsoft.Json code to System.Text.Json

I don' t understand what are you trying to reach but I deserialized it this way using System.Text.Json. var jsonElement = JsonDocument.

Migrating An API from Newtonsoft.Json to System.Text.Json

... I've been looking to migrate an API from using the Newtonsoft.Json serialization library to the newer, Microsoft one, System.Text.Json.

Using System.Text.Json alongside Newtonsoft Json.Net

In June 2019, Microsoft introduced System.Text.Json as a feature of .NET (core) 3.0 to the public. The reason they gave for creating this ......