.NET 8 and .NET 9 End of Support: What It Means for nopCommerce Stores

Your hosting provider sends a one-line notice: .NET 9 loses support on 10 November. Your store runs nopCommerce 4.90, it took orders this morning, and nothing in the admin looks different. Is this a deadline, or just a date on a vendor's calendar?

Microsoft announced on 29 June 2026 that both .NET 8 and .NET 9 reach end of support on 10 November 2026. For a nopCommerce store that matters, because the platform sits directly on that runtime: 4.70 runs on .NET 8, and 4.80 and 4.90 run on .NET 9.

When we plan an upgrade at BSS, the runtime is the first thing we read off the server, before plugins or themes. This guide does the same for your store: what stops, which versions are affected, what the risk honestly looks like, and a plan for the week.

For the other side of the story, why 5.0 moved to .NET 10, read nopCommerce 5.0 on .NET 10.

What Actually Stops on 10 November 2026

Start with what does not happen. Microsoft says apps built on .NET 8 or .NET 9 will keep running after the date, so your store does not switch off.

.NET 8 was a Long Term Support release, supported for 36 months from November 2023. .NET 9 was a Standard Term release that Microsoft extended from 18 months to 24, so both end on the same day.

One detail helps you plan. 10 November is also a Patch Tuesday, and Microsoft says each version may get one final update that day if a critical issue is known. Install the latest patch before then: on Microsoft's support policy page, updated 25 October, that was 8.0.33 for .NET 8 and 9.0.22 for .NET 9.

There is a catch before the date, too. Microsoft's support policy says a system must stay current on released patches to qualify for support, so a server still on an old 8.0 or 9.0 build is already outside it. Patching is the cheapest step you can take this week, whatever you decide next.

Which nopCommerce Versions Sit on These Runtimes

Now map the date to your store. nopCommerce sets its target runtime in its own source, so we read it from each release tag on the project's GitHub repository.

Read the table from the bottom. Only 5.00 sits on a runtime that stays supported after 10 November, and every version from 4.50 to 4.90 is on one that has ended or is about to. A store older than 4.50 has a longer road, and our guide to upgrading nopCommerce to 4.90 is the place to start.

The layers in the picture explain why this matters even when your own code is fine. Your plugins and theme stand on nopCommerce, nopCommerce stands on the runtime, and the runtime is the layer that stops receiving fixes.

Check what your server actually runs

Read the nopCommerce version under System, System information in the admin, then list the runtimes on the server:

dotnet --list-runtimes
# Look for lines such as:
# Microsoft.AspNetCore.App 9.0.x [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]

On Docker, read the image tag instead. A server can hold several runtimes at once, so check every server that serves the store, staging included.

From the BSS team

Before we plan an upgrade at BSS, we start from two facts anyone can read in minutes: the nopCommerce version in the admin and the runtimes installed on the server. Our nopCommerce upgrade checklist follows the same order.

What the Risk Honestly Looks Like

So nothing breaks on 11 November, and that is exactly why the date is easy to ignore. The risk is slower than a crash: your store keeps selling on a platform that no longer receives fixes.

Hosting is the question owners skip. Ask three things: which runtimes are installed today, whether the host plans to remove .NET 8 and .NET 9 after the date, and who installs .NET 10 if you move. A managed host that answers clearly is worth keeping, and one that cannot answer is a risk of its own.

This is the point where many owners bring in a developer to size the move. You can hire a .NET developer from BSS to audit your extensions and port the ones that block 5.00.

Your Options: Move, Port or Hold

Once you know where you stand, there are three honest paths. Choose one on purpose, because drifting into the third is what happens when nobody decides.

For most stores the supported route is nopCommerce 5.00, which moves the platform to .NET 10. Our guide to upgrading 4.90 to 5.0 covers the three gates and the rollback set, and stores on 4.80 or older finish the 4.90 upgrade first.

The third path deserves a warning. Microsoft's advice for your own apps is to change the target framework to net10.0, but nopCommerce supports .NET 10 through 5.00, and we have not tested 4.90 on .NET 10.

If you wrote a custom plugin for 4.80 or 4.90, the port starts with one line in the project file, net9.0 to net10.0, and the real work is the API changes after it. Our guide to porting a nopCommerce plugin from 4.90 to 5.0 walks through that list.

If you hold, hold with a date. Install the last .NET patch, keep the operating system and web server current, and put the move in the calendar. That is a plan, not a fix, because nothing will patch a new runtime flaw for your version.

From the BSS team

We build our plugins for each nopCommerce release at BSS, which is why some already list 5.00 builds on their product pages. For a store, the extension list is the gating item, so we ask for it on day one. Our team runs nopCommerce version upgrades from that list.

A Plan for the Week of 10 November

Whichever path you pick, the first week looks the same. Work down this list and you will know your position before the date passes.

The extension list is usually what sets the date, and payments come first. For stores that use Stripe, one name is quick to tick off.

BSS plugin

BSS Stripe Payment

Connects nopCommerce checkout to Stripe, and its product page lists 5.00, 4.90 and 4.80 builds, so one gateway is checked off for a move.

View the plugin

For the rehearsal step, use our guide to testing plugin and theme compatibility before an upgrade as the gate, and check your server against the 5.0 hosting requirements before the cutover.

Frequently Asked Questions

Final Thoughts

Go back to that notice from your host. Your store will take orders on 11 November exactly as it did on the 9th, and now you know what changed underneath it: the runtime stops getting fixes.

The decision in front of you is small and specific. Move to 5.00, port the gaps that block you, or hold with a date, and write the answer down this week. If you would rather hand the check and the move to a team that does upgrades, send us your version and extension list.