.NET
2 Charts Explaining .NET Long-Term Support
.NET 8 was released on November 14, 2023, bringing much excitement to the DevOps community. So what does that mean for .NET Core 2.1, .NET Core 3.1, .NET Framework 4.8, .NET 5…?
There’s a lot to keep track of! Microsoft has scattered the information across a variety of GitHub pages, blog posts, and announcements, so it’s hard to know what’s still supported and what’s been deprecated.
Instead of cross-checking various docs, use these handy charts we’ve made to understand how your .NET set-up is being supported right now.
.NET Framework
| Version | Existing Support | Support End Date |
| 1.x | ✘ out of support | |
| 2.x | ✘ out of support | |
| 3.x | ✘ out of support | |
| 3.5 | ✓ Operating System | ⚠️ 2029 (April) |
| 4.0 to 4.6.1 | ✘ out of support | |
| .NET Core 1.0 – 3.1 | ✘ out of support | |
| 4.6.2 to 4.7 | ⚠️Operating System (mixed) – review support policy of each version | ⚠️ Varies (mixed) |
| 4.8 | ✓ Operating System | ✓ Indefinite (2031+) |
Any developers using an out-of-support .NET should consider migrating to .NET 8 as soon as possible.
Any developers using a yellow-warning .NET, or running applications on deprecated frameworks like Windows Communication Framework, should target with caution and start considering a migration plan.
.NET 5 and Beyond
| Platform | Release Date | Support End Date |
| 5 | November 2020 | ⚠️2022 (May) |
| 6 | November 2021 | ✓ 2024 (November) |
| 7 | November 2022 | ⚠️ 2024 (May) |
| 8 | November 2023 | ✓ 2026 (November) |
| 9 | November 2024 (Projected) | ✓ 2026 (May) (Projected) |
All odd-numbered. NETs, since .NET 5, will be “current” and only have support for 18 months after their release. Compared to even-numbered .NETs like .NET 6 and .NET 8 which will have approximately three years of support from release.
Understand Your .NET’s Support Status
Although .NET Framework 3.5 and 4.8 are estimated to last another 10 years, it never hurts to start planning for migration. Consider how you’ll move your package libraries; now may be the time to consider a CI/CD method.
Did you find this article helpful? Are you using NuGet to make your .NET packages? Learn how to optimize your NuGet in the Enterprise; sign up for our free NuGet guide:
