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 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
Why I skipped ASP.NET Core 3.0 ?
I have waited for ASP.NET Core 3.1 and .NET Core 3.1 before migrating for severals simple reasons:
As you may know ASP.NET Core 3.0 and .NET 3.0 have been released in September 2019 and their respective 3.1 version on December 2019.
I did not want to migrate twice in 3 months but it’s not the most important thing, migrate to version 3.0 was useless because there is no long time support for .NET 3.0, for .NET Core 3.1, that’s the case.
Unlike .NET Core 2.1 (LTS), .NET Core 2.2 a Long Time Support, so it was the occasion to migrate to a LTS version of .NET Core
Here is a summary of each version and their support by Microsoft:
|Version||Release date||Support level||End of support|
|.NET Core 3.1||12-03-2019||LTS||12-03-2022|
|.NET Core 3.0||09-23-2019||STS||03-03-2020|
|.NET Core 2.2||12-04-2018||STS||12-23-2019|
|.NET Core 2.1||05-30-2018||LTS||08-21-2021|
|.NET Core 2.0||08-14-2017||EOL||10-1-2018|
|.NET Core 1.1||11-16-2016||EOL||06-27-2019|
|.NET Core 1.0||06-27-2016||EOL||06-27-2019|
LTS: Long Time Support
STS: Short Time Support
EOL: End of Life
What you need to do before reading the next articles ?
As you can guess, before reading the next three articles, you will need to:
- Download and install Visual Studio 2019 version 16.4 or higher.
- Download and install .NET Core 3.1
- Upgrade your projects to .NET Core 3.1 , because ASP.NET Core 3.1 requires it.
- Update your Nuget packages to a version compatible with ASP.NET Core 3.1