You can feel free to jump all the way if you want. Some folks are more little methodical about this, upgrading first to 3.0 and then to 3.1. You'll likely not have anything like this, but be aware. Also note that I have a custom IISUrlRewrite.xml that I want to make sure gets to a specific place. You'll note that most of it is deletions. So I'll start at the migration docs here to go from 2.2 to 3.0.NET Core 2.2 reaches "end of life" (support) this month so it's a good time to update to the 3.1 version that will be supported for 3 years.Īnd my 3.0 updated csproj. ![]() I can tell because the csproj has a "TargetFramework" of netcoreapp2.2. NET Core 3.1įirst, it seems my main homepage is NET Core 2.2. For my podcast site and main site I honestly have forgotten what version of. I'm not sure about you, but for me, when I don't look at some code for a few months - in this case because it's working just fine - it takes some time for the context switch back in. You can read about what LTS means but quite simply it's that "LTS releases are supported for three years after the initial release." ![]() NET Core 3.1 is out just this last week and it is a "LTS" or Long Term Support version, I thought it'd be a good time to update my main site and my podcast to.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |