timetobail
My stack

.NET · Forced move · Announced June 29, 2026 · Sources checked Oct 13

Time to bail on .NET 8 and .NET 9 apps?

Time to Bail · Boarding pass

From.NET 8 and .NET 9 apps
ToYour pick

Act. You can stay.

.NET 8 and .NET 9 get no security fixes after November 10, 2026. Move to .NET 10.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
End of support
Time left
25days
Status
Act

.NET 8 and .NET 9 end of support: November 10, 2026

.NET 8 and .NET 9 both reach end of support on November 10, 2026. After that, Microsoft sends no security fixes for them. Microsoft says to move to .NET 10.

How it is winding down

  1. Jun 29AnnouncedDone
  2. Nov 10End of supportNext

What to do before November 10

Tick steps as you go. Your progress stays in this browser.

  1. Find apps on .NET 8 and 9

    Check the TargetFramework in each project file. Look for net8.0 and net9.0.

  2. Change the target to .NET 10

    Set TargetFramework to net10.0 and update your NuGet packages.

  3. Update build and hosting, then test

    Use the .NET 10 SDK and runtime where you build and host. Run your tests and ship before November 10.

Facts we checked

Facts and their sources
End of supportNovember 10, 2026[1]
Versions.NET 8 and .NET 9[1]
After that dateNo servicing updates, security fixes or technical support from Microsoft[1]
Last updateEach may get one final update on November 10, 2026 if there is a known critical issue[1]
Upgrade target.NET 10, an LTS release supported through November 2028[1]
How to upgradeSet TargetFramework to net10.0 (from net8.0 or net9.0)[1]
AnnouncedJune 29, 2026[1]
Azure FunctionsIn-process support ends the same day, November 10, 2026[2]
Apps on .NET 8 or .NET 9Get no security fixes after November 10, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. .NET 8 and .NET 9 end of support Microsoft · primary · checked Oct 13
  2. Migrate C# apps from the in-process model to the isolated worker model Microsoft · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on .NET 8 and .NET 9 apps? Act. You can stay. .NET 8 and .NET 9 get no security fixes after November 10, 2026. Move to .NET 10.

On our scale this is Act: change a setting or plan before the date. You can stay.

.NET 8 and .NET 9 both reach end of support on November 10, 2026. After that, Microsoft sends no security fixes for them. Microsoft says to move to .NET 10.

Here are the facts we checked:

  • End of support: November 10, 2026 (Microsoft)
  • Versions: .NET 8 and .NET 9 (Microsoft)
  • After that date: No servicing updates, security fixes or technical support from Microsoft (Microsoft)
  • Last update: Each may get one final update on November 10, 2026 if there is a known critical issue (Microsoft)
  • Upgrade target: .NET 10, an LTS release supported through November 2028 (Microsoft)
  • How to upgrade: Set TargetFramework to net10.0 (from net8.0 or net9.0) (Microsoft)
  • Announced: June 29, 2026 (Microsoft)
  • Azure Functions: In-process support ends the same day, November 10, 2026 (Microsoft)
  • Apps on .NET 8 or .NET 9: Get no security fixes after November 10, 2026 (Microsoft)

You can stay on .NET. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. .NET has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps on .NET 8 or .NET 9: Get no security fixes after November 10, 2026.

The date to remember is November 10, 2026. Make the change before then.

What to do before November 10

  1. Find apps on .NET 8 and 9. Check the TargetFramework in each project file. Look for net8.0 and net9.0.
  2. Change the target to .NET 10. Set TargetFramework to net10.0 and update your NuGet packages.
  3. Update build and hosting, then test. Use the .NET 10 SDK and runtime where you build and host. Run your tests and ship before November 10.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on .NET 8 and .NET 9 apps can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product