Per Bjurström
Oct 19, 2018
  7195
(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

Please login to comment.
Latest blogs
Building a Custom RAG for Optimizely Opal

How to design a standalone RAG service for documents that don't belong in Optimizely One, and expose it to Opal and other AI tools without coupling...

Michał Mitas | May 14, 2026 |

Semantic Search - Deep Dive

Deep dive into semantic search with Optimizely Graph

Michał Mitas | May 14, 2026 |

Building a Custom RAG for Optimizely Opal

Opal's built-in knowledge is limited to content inside Optimizely One. Here's how to design a custom RAG service for documents that live outside th...

Michał Mitas | May 14, 2026 |

The Fragment Conundrum

Explore the challenges and opportunities of working with Optimizely SaaS, GraphQL fragments, and headless CMS architectures. Learn practical...

Andy Blyth | May 13, 2026 |

Optimizely CMS 13: What Actually Changed and Why It Matters

I had the privilege of attending a deep-dive session on CMS 13 this week, and after seeing the full roadmap laid out across these slides, I wanted ...

Aniket | May 12, 2026

Introducing the Optimizely MCP Server: AI That Speaks Commerce

MCP AI Commerce B2B Claude ChatGPT OpenAI Optimizely Insite Commerce Introducing the Optimizely MCP Server : AI That Speaks Commerce We've connecte...

Vaibhav | May 12, 2026