Quan Mai
May 14, 2018
visibility 6242
star star star star star star
(8 votes)

Commerce no longer supports WebForms

If you need an extra push to move your WebForms websites to MVC or, even more "modern" SPA - then here it is: Commerce 12.0 is the last version tested with WebForms. We dropped testing Commerce on WebForms from 12.1 onward. By "Drop testing", I mean we no longer test new version of Commerce on our WebForms template (if you worked with Commerce 7.5, you probably know about Commerce Sample site. Well, that had been updated and used for WebForms testing, until now). QuickSilver will be used for our primary and only template for testing new features, bug fixes, as well regression for Commerce.

What does that mean for you?

  • For new projects, it's almost certain that you will start with MVC/SPA anyway.
  • For existing projects, it's likely you already migrated if you upgraded to Commerce 12+
  • For projects that not yet migrated (which should be a very very minority, if any), it will not suddenly stop working. It will most likely continue working as usual without any problems. However, we won't guarantee that, and if you runs into issues (which is very very unlikely), we will not fix those WebForms-specific bugs.

This is more of a "good to know" annoucement that has very little impact (if at all) on your daily work. So MVC (and/or SPA) are what you should be looking at now.

May I say "WebForms support is dead, long live MVC/SPA"? :)

May 14, 2018

Comments

Linus Ekström
Linus Ekström May 18, 2018 12:07 PM

Finally - congratulations Commerce development team!

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |