.NET Versioning — Which Version to Use
Release Cycle
Microsoft releases a new .NET version every November.
Even numbers = LTS (Long Term Support) → 3 years support
Odd numbers = STS (Standard Term Support) → 18 months support
.NET 6 (Nov 2021) → LTS → End of support: Nov 2024
.NET 7 (Nov 2022) → STS → End of support: May 2024
.NET 8 (Nov 2023) → LTS → End of support: Nov 2026 ← USE THIS
.NET 9 (Nov 2024) → STS → End of support: May 2026
.NET 10 (Nov 2025) → LTS → End of support: Nov 2028 ← upcoming
Which Version to Use?
Production (new project) → .NET 8 (LTS, supported until Nov 2026)
Latest features/learning → .NET 9
Legacy maintenance → Keep on its current version
Job market → .NET 8 (most common in interviews 2024-2025)
Target Framework Monikers
<!-- .csproj — specify .NET version -->
<TargetFramework>net8.0</TargetFramework> <!-- .NET 8 -->
<TargetFramework>net8.0-windows</TargetFramework> <!-- .NET 8 Windows only -->
<!-- Multi-target -->
<TargetFrameworks>net8.0;net9.0</TargetFrameworks>
Checking Runtime Version in Code
🤖Use AI to Learn Faster
Use ChatGPT, Claude, or Copilot to go deeper on .NET versioning and LTS. Try these prompts:
"What is the difference between LTS and STS in .NET?""Which .NET version should I use for a new production project in 2025?""How often does Microsoft release new .NET versions?""What happens when .NET version reaches end of support?"
💡 Tip: After reading this article, paste your own code into AI and ask "What could go wrong here and why?" — fastest way to find edge cases and deepen understanding.
nexcoding.in
Have questions on your tech stack, ongoing projects, or need one-to-one training?