Microsoft has announced that starting January 2026, the C# Dev Kit and C# VS Code extension will no longer support development using the .NET 6 and .NET 7 SDKs. In the blog post below, I’ll walk you through what teams running these versions of .NET in production need to know.
VS Code Support
The January 2026 release of the C# Dev Kit for VS Code will drop support for the .NET 6 and .NET 7 SDKs. If you continue developing with those SDKs in VS Code, you can expect:
- Degraded IntelliSense and code navigation
- Debugging and project system issues
- Bugs that will not be fixed
Microsoft recommends using a supported SDK such as .NET 8 or later for development, even if you are targeting older frameworks.
.NET 6 and 7 Are Already Out of Support
This tooling announcement is a follow-on effect, not a new policy change. Both of these versions of .NET have already been out of support for a while:
- .NET 6 reached end of support in May 2024
- .NET 7 reached end of support in November 2024
Being out of support means that these frameworks no longer receive security patches, runtime fixes, or official support. Applications will continue running, but they are doing so outside Microsoft’s support window.
Visual Studio Support
If you are using Visual Studio, your existing applications will continue to work. You can still:
- Open, build, run, and debug projects targeting .NET 6 and .NET 7
- Maintain legacy solutions without immediate disruption
However, Visual Studio compatibility does not change the underlying support status of the framework. Over time, newer IDE features, libraries, and tooling will increasingly assume .NET 8 or later. As of today, Microsoft supports the following .NET versions:
- .NET 8 (LTS) — supported through November 2026
- .NET 9 (STS) — supported through May 2026
- .NET 10 (LTS) — released November 2025, supported through November 2028
Any application targeting .NET 7 or earlier should be considered out of support and be updated as soon as reasonably possible.
What to Do With a .NET 7 Or Earlier App
In many cases, getting back into support does not require a rewrite. At a minimum:
- Install a supported SDK (for example, .NET 8, 9, or 10)
- Upgrade the application’s target framework to a supported version
In real-world systems, this usual also includes:
- Updating dependencies and build pipelines
- Addressing deprecated APIs
- Validating security, performance, and behavior changes
- Aligning CI/CD and hosting environments with modern .NET practices
This is where a simple upgrade can become a broader modernization effort. This is often easier for more recent versions of .NET, and more time-consuming for older ones. Having experience with this process can be helpful. That’s where Trailhead comes in.
Trailhead Can Help
Trailhead often helps teams move from out-of-support to future-ready with minimal risk. We work with teams to:
- Assess upgrade readiness and technical risk
- Define safe, incremental upgrade paths
- Modernize architecture and tooling where it delivers value
- Align framework upgrades with business goals and timelines
If you’re running .NET 6 or 7 and want a clear path forward, Trailhead can help you get back into support. Simply contact us to get started!


