Bien Nguyen
May 25, 2026
  791
(5 votes)

Optimizely CMS 12 Now Fully Supports .NET 10

This is the latest installment in our ongoing series covering .NET version support for Optimizely products. If you've been following along, you may have read our earlier posts on this topic:

As the .NET ecosystem continues to evolve, staying current with supported frameworks is essential for security, performance, and long-term maintainability. We're pleased to confirm that Optimizely CMS 12 is fully compatible with .NET 10, and we encourage all customers to begin planning their upgrade path.

Why This Matters: .NET 8 and .NET 9 Are Approaching End of Support

Microsoft has confirmed that both .NET 8 and .NET 9 will reach end of support on November 10, 2026 (see this for more detail). Both have already entered the Maintenance phase, meaning updates are limited to security patches only. .NET 10, released November 11, 2025, is the current LTS release with support through November 2028 - giving you over two additional years of coverage.

CMS 12 and .NET 10: What You Need to Know

After thorough verification, we can confirm that CMS 12 is fully compatible with .NET 10. Our testing included CMS 12 sites with popular add-ons such as Optimizely Forms and Language Manager installed, and we can confirm that these add-ons work as expected on .NET 10 as well. Here's what you need to know about upgrading:

Recommended Package Versions

For the best experience, we recommend updating to the following package versions (or higher):

Package Minimum Recommended Version
EPiServer.Cms.Core 12.24.0
EPiServer.Cms.UI 12.34.4

These versions include dependency updates that resolve two known vulnerability warnings when running on .NET 10.

Running on Earlier CMS 12 Versions

If you are running an earlier version of CMS 12, the good news is that .NET 10 compatibility is not limited to the latest packages. Previous CMS 12 versions work with .NET 10 as well. However, you may encounter two dependency vulnerability warnings during build or restore. These warnings do not affect functionality but should be addressed for a clean security posture.

You have two options:

  1. Upgrade to the recommended CMS versions above - the simplest path, as the vulnerability warnings are resolved automatically.
  2. Manually update the affected dependencies - if upgrading CMS packages immediately is not feasible, you can resolve the warnings by updating the vulnerable transitive dependencies directly in your project file.

What About Commerce 14?

For customers running Optimizely Commerce 14 (Commerce Connect), please note that .NET 10 support is not yet available. We'll work on updating Commerce 14 (and relevant Commerce-specific addons) to support .NET 10, and expect to release a supported version of Commerce 14 for .NET 10 in late Q2 / early Q3 2026. We’ll share a follow-up announcement once the work is complete.

In the meantime, Commerce 14 customers should continue running on .NET 8 and monitor this space for updates.

Our Recommendation

We encourage all CMS 12 customers to target .NET 10 for new projects and begin planning upgrades for existing solutions. With .NET 10 being an LTS release supported through November 2028, it provides a stable, long-term foundation for your digital experience platform.

By upgrading now, you benefit from:

  • Extended support - over two additional years of framework support compared to .NET 8 and .NET 9.
  • Performance improvements - each .NET release brings meaningful runtime and compilation enhancements.
  • Security - staying on a supported framework ensures you receive critical security patches.

Need Help?

If you have questions about upgrading to .NET 10 or encounter any issues, our support team and developer community are here to help. Visit the Optimizely Developer Documentation for the latest system requirements, or reach out to Optimizely Support for direct assistance.

May 25, 2026

Comments

Mark Stott
Mark Stott May 26, 2026 02:35 PM

If those versions had actually been compiled as .NET 10 I would have found a way to give you more than 5 stars ✨😊

But it's great to hear we can bump our customers onto the latest versions of .NET.

Piotr
Piotr May 27, 2026 02:46 PM

Great to see official .NET 10 support in CMS 12 👏 Just went through a large-scale upgrade across multiple solutions and can confirm – most of the work is in the dependency graph, not the framework switch itself.

I’ve shared a few practical lessons from the field here: https://lnkd.in/dpKa8-5w

Please login to comment.
Latest blogs
Introducing the Optimizely MCP Server: AI That Speaks Commerce Part-II

— Part 2 · Build Update · B2B Commerce From conversation to completed transaction. Part 1 gave AI the ability to speak commerce. The latest release...

Vaibhav | May 29, 2026

Finding Thomas Part 1 - The Observation Post

Meet Thomas Thomas is the returning visitor who has been to your site forty times but has never filled out a form. He opens every newsletter but...

Ritu Madan | May 28, 2026

Extending the Optimizely 11 Link Validation job with custom exclude patterns

This might be common knowledge but I have never done this in all my years working with Optimizely solutions. On a customer I noticed that the link...

Per Nergård (MVP) | May 28, 2026

Optimizely SaaS Visual Glossary

Recently I came across Optimizely SaaS CMS Glossary: https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/glossary...

Kiran Patil | May 28, 2026 |