Per Bjurström
Oct 19, 2018
visibility 7491
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
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |