Quan Mai
Optimizely
May 14, 2018
visibility 6440
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
Why your GeoPoint never reaches Optimizely Graph, and how to fix it

Geo search lets Optimizely Graph match and rank content against geographic coordinates, so applications can deliver location-aware experiences such...

K Khan | Nov 11, 2026

Mark goes desktop: what's new in Optimizely Agent Platform, November 2026

Optimizely's November release for Mark, the Optimizely Agent Platform, is one of the most significant updates since the platform launched. Two...

Scott Reed | Nov 11, 2026

Upgrading Optimizely CMS 13 from .NET 10 to .NET 11

How to upgrade Optimizely CMS 13 to .NET 11, including a workaround for edit mode and an Azure gotcha.

Tomas Hensrud Gulla | Nov 11, 2026 |

Making Built-in CMS Categories Queryable in Optimizely Graph (CMS 13 PaaS)

With Optimizely CMS 13 PaaS, Optimizely Graph replaces Search & Navigation as the content query engine. However, if your existing CMS solution reli...

Mardy | Nov 10, 2026