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.