- My migration experience from ASP.NET Core 2.2 to 3.1, part 1: Introduction
- My migration experience from ASP.NET Core 2.2 to 3.1, part 2: Changes in Program.cs
- My migration experience from ASP.NET Core 2.2 to 3.1, part 3: Changes in Startup.cs
- My migration experience from ASP.NET Core 2.2 to 3.1, part 4: Changes in the rest of the application
Changes in the rest of the application
.NET Core 3 introduces a new serializer
Json.Net (NewtonSoft) has been for a long time the most used JSON serializer in .NET world. Since .NET Core 3, Microsoft introduced a new one named System.Text.Json. Because it provides better performance I decided to rewrite my JSON serializer service.
My JSON serializer service with Json.Net (NewtonSoft):
My JSON serializer service with System.Text.Json:
If you want to do the same you can download the package here and rewrite our serializations like I did:
If you want to learn more about it, you can red this nice blog article here: https://www.c-sharpcorner.com/article/the-new-json-serializer-in-net-core-3/
This article concludes my migration to ASP.NET Core 3.1.
This is was my migration experience only, I did not cover everything, if you want to learn more about migration for ASP.NET Core 2.2 to 3.0 you can read this article here and from ASP.NET Core 3.0 to 3.1 you can read this other article here.
Hope this serie of articles helped you 🙂