loading...
Cover image for Update Your .NET Core Projects, Folks!

Update Your .NET Core Projects, Folks!

dotnetcoreblog profile image Jamie Updated on ・2 min read

the header image for this post was taken from the official Support Policy for .NET Core

It's finally that time! Yes: .NET Core 1.0 and 1.1 have gone out of LTS and are no longer receiving servicing support from Microsoft.

What Does That Mean?

Well, you should have already upgraded you projects to (at least) .NET Core 2.1 (though 2.2 is preferred). Which means you don't need to read this article.

Yay!

But for those of you who haven't upgraded: now is the time to do it. Seriously, talk to your project managers/project owners/clients/whoever and tell them that you need to take the time to upgrade to a supported version of .NET Core.

It's up to you what you do if they don't want to give you the time. But personally, I wouldn't want to support an application stack which was written against an unsupported framework.

For some, the upgrade path will be super simple: edit the csproj, up the version of the Target Framework Moniker to 2.1 or 2.2, hit build, voilà!

thanks to Paul Seal for pointing out my typo here 🎻

For others it will be a little painful and might mean changing some things.

Either way, it'll be worth taking a look at the 1.x to 2.x migration guide found in the docs.

Also, it's worth knowing what the support dates are for .NET Core. That way you can plan around migrating your projects to ensure that they stay supported.

Posted on by:

dotnetcoreblog profile

Jamie

@dotnetcoreblog

Serial podcast creator and .NET Core maniac. Can often be found talking about everything and nothing on one of the many podcasts that he produces (only one of them is about .NET Core, honest)

Discussion

markdown guide
 

"you should have already upgraded you projects to (at least) .NET Core 2.1 (though 2.2 is preferred). "
Given that 2.1 is the lts and not 2.2 I don't think it's reasonable for people still on
1.x to prefer 2.2 over 2.1.

 

Whilst I agree, I'll point out that support for .NET Core 2.2 ends in December this year (as per the support docs I linked in the article).

2.1 is a special case,

disclaimer: I do not work for Microsoft, and the following is based on blog posts and episodes of the ASP.NET Community Standup

as ASP.NET Core 2.1 on .NET Framework 4.6+ is going to be supported for a little longer, in order to allow folks time to transition over from Framework to Core. But even that support will end in 2021, at which point .NET Core 3.0 will be the LTS before .NET 5 gets that level of support.

I'm told that, after that time, .NET will have a rolling LTS similar to Node.

Again, I'm not a Microsoft employee or representative. These are just points taken from articles and Community Standups.