.NET 6 LTS Ends Nov 12—3 Paths to Take

.NET 6 LTS End of Life: Three Paths Forward

Microsoft .NET 6 (LTS) reaches its end of life on November 12, 2024. With about nine months remaining, IT leaders face a clear decision window. The latest version in this line, 6.0.36, will receive no further updates after that date — no security patches, no bug fixes, no vendor support of any kind.

For organizations running .NET 6 on production servers, the question isn't if to act but which path to take. Below we assess the three realistic options: migrate, buy vendor extended support, or move to third-party maintenance.

Option 1: Migrate or Upgrade to .NET 8 (LTS)

The vendor-recommended path is to upgrade to .NET 8, the current LTS release. Microsoft offers tooling to assist migration, and .NET 8 brings performance improvements and new language features.

Cost profile:

• Internal development time for migration testing, code changes, and deployment.
• No direct licensing cost if you are already on a current support agreement.
• Potential need for new OS or infrastructure compatibility work.

Risk:

• Moderate to high for complex or poorly documented codebases.
• Risk of breaking changes in library dependencies, custom frameworks, or third-party integrations.
• Requires staging, QA, and rollback planning.

Timeline:

• Nine months is generally sufficient for a well-resourced team, provided migration begins within the next 60–90 days.

Best suited for:

• Applications under active development where new features justify the upgrade effort.
• Teams with dedicated .NET expertise and automated testing.
• Environments where staying current with the vendor roadmap is a compliance or strategic requirement.

Option 2: Purchase Microsoft Extended Support (if available)

Microsoft historically offers paid Extended Support for some LTS releases. At the time of writing, Microsoft has not formally announced Extended Support terms for .NET 6. If offered, it would likely cover security fixes only, for a limited period (typically one to three years), at a premium cost per-core or per-server.

Cost profile:

• Annual subscription fee, often significantly higher than standard support.
• No development or migration cost if you intend to stay put.

Risk:

• Low — you remain under vendor support for critical vulnerabilities.
• Risk that terms change or are not extended again.

Timeline:

• Can be arranged up to the EOL date. No code changes required.

Best suited for:

• Regulated industries that require a vendor-supported path but cannot afford downtime for migration right now.
• Short-term bridge while planning a phased upgrade.

Check your Microsoft licensing agreement or account team for current Extended Support availability for .NET 6.

Option 3: Move to Third-Party Support

Third-party support providers, including 3rd Part Support, can continue delivering security patches and bug fixes for .NET 6 after Microsoft's EOL date. This approach keeps the runtime stable without requiring migration or vendor-paid extended support.

Cost profile:

• Typically 30–50% less than Microsoft's Extended Support (if offered).
• No migration or upgrade project cost.
• Fixed annual fee with no per-core/per-server complexity.

Risk:

• Low for stable workloads that are not under active development.
• No exposure to new features or platform evolution — but that's the point.
• Requires due diligence on the provider's patch engineering and SLAs.

Timeline:

• Can be initiated immediately and continue indefinitely. No code changes.

Best suited for:

• Legacy applications that are stable and have no feature roadmap.
• Cost-sensitive environments where the upgrade ROI is negative.
• Orgs that want to defer migration 2–3 years while maintaining security and compliance.

Decision Checklist

Use this short guide to match your situation to the right path.

Criterion	Migrate to .NET 8	Vendor Extended Support	Third-Party Support
Application active development?	Yes	No (or minimal)	No
Upgrade budget available?	Yes	Maybe (avoid migration cost)	No (want to minimize spend)
Vendor compliance required?	Yes	Yes	Verify provider's compliance coverage
Timeline flexibility?	Start now	Can wait until EOL	Start any time
Risk tolerance for breaking changes?	Acceptable	Low (no changes)	Low (no changes)

Summary

Nine months is enough time to execute any of the three paths. Migrating to .NET 8 makes sense for teams with active development roadmaps. Vendor Extended Support (if offered) buys a short-term bridge. Third-party support is a cost-effective, low-risk option for stable workloads that simply need continued patching.

For organizations evaluating third-party maintenance, contact us to discuss how we can support your .NET 6 environment past November 2024.