Lessons learned: From Newtonsoft.Json to System.Text.Json in Large Codebases

From the creator

In this session, I'll discuss something that may seem completely trivial - replacing a JSON parser in a large codebase. A year ago, we decided to switch from Newtonsoft.Json to System.Text.Json in an open-source framework. Because we had a lot of custom converters, used advanced concepts such as JSON patching, encrypting parts of the object tree, and relied on several unique features of Newtonsoft.Json, it has become a long and complex journey. I'll discuss the differences between the two libraries, what we learned, and how the change improved the framework's performance and memory efficiency. 🎥 See more from .NET Conf: https://aka.ms/dotnetconf-playlist 🔗 Links: .NET 10 — The most intelligent and unified .NET yet: https://aka.ms/dotnet10/ .NET Aspire 13 — Simplified orchestration for cloud-native apps: https://aka.ms/aspire13/announcement ASP.NET Core 10 — Modern, secure, and full-stack web development: https://aka.ms/asp/dotnet/2025 .NET MAUI 10 — Build beautiful apps on every platform: https://aka.ms/dotnet/maui/2025 C# 14 — A more expressive and productive language: https://aka.ms/csharp14/announcement/2025 F# 10 — Safer, faster, and more functional than ever: https://aka.ms/fsharp10/2025/announcement Visual Studio 2026 — Faster, smarter, and built for the future: https://aka.ms/visualstudio2026/announcement 🎙️ Featuring: Tomáš Herceg (@hercegtomas) Connect with .NET: Blog: https://aka.ms/dotnet/blog Twitter: https://aka.ms/dotnet/twitter TikTok: https://aka.

Published 2025-11-14 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.