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)
Location
Leeds, UK
Education
Computer Science with Games Development - BSc
Work
.NET Development Contractor; Podcast host, producer and editor
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.