Per Bjurström
Optimizely
Oct 19, 2018
visibility 7555
star star star star star star
(13 votes)

CMS drops support for WebForms

This is an early heads up that CMS 11.x will be the last generation of CMS with support for building templates on ASP.NET WebForms. When the ASP.NET MVC support was launched with Episerver 7 back in 2012 it quickly became the technology of choice for building modern web sites, some of our newer modules since such as Forms only supports MVC and Commerce dropped support for WebForms earlier this year. Today all new sites are either built on ASP.NET MVC or as a SPA.

For sites built on WebForms we will continue to support them on the CMS 11.x generation. There will be no breaking change release of CMS this year.

Oct 19, 2018

Comments

Henrik Fransas
Henrik Fransas Oct 19, 2018 07:53 AM

Thanks for the heads up Per!

Linus Ekström
Linus Ekström Oct 19, 2018 08:06 AM

Finally!

Erik Täck
Erik Täck Oct 19, 2018 08:09 AM

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!11

Oct 19, 2018 08:14 AM

YEAAAHHH!

Per Atle Holvik
Per Atle Holvik Oct 19, 2018 08:34 AM

Any chance that CMS 12 will get .NET Core suppport? :)

valdis
valdis Oct 19, 2018 12:34 PM

what are webforms and why drop?

Mark Bagnall
Mark Bagnall Oct 19, 2018 12:51 PM

Does this mean all the current Admin mode .aspx pages will be rewritten?

Robin Lindbladh
Robin Lindbladh Oct 19, 2018 05:54 PM

Finally!

Quan Mai
Quan Mai Oct 22, 2018 06:12 AM

@Mark : I don't think that is the case. By dropping WebForms support we mean we will not test our framework with WebForms template and any bugs related to WebForms found will not be fixed. It is very likely that anyWebForms sites will continue working as usual 

Luc Gosso (MVP)
Luc Gosso (MVP) Oct 22, 2018 09:51 AM

Automatically migrate webform pages to MVC views

For you who is stuck in webforms AND who dears, there is a way to automatically migrate webform pages to MVC views in Episerver.

I wrote a series of blog posts once, about it, on how to convert your webforms pages to MVC views, incl ascx to cshtml. You'll find it here (https://devblog.gosso.se/tag/webforms/)

Still, my recommendation is to start new, if you have any hesitation which way to go, pls contact me!

Regards Luc

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026