News

Microsoft: Web Forms Is No Silverlight

The death of Web Forms has been greatly exaggerated.

In an announcement of the new Visual Studio 2022 17.2 GA release, a developer comment questioned Microsoft's investment in Web Forms, likening it to the controversial deprecation of Silverlight (see "A Decade Later, .NET Developers Still Fear Being 'Silverlighted' by Microsoft").

Let It Go
[Click on image for larger view.] Let It Go (source: Telerik).

A Microsoft senior program manager quickly set him straight.

Here's the comment:

I'm confused about why you guys are investing in Web Forms tooling. Isn't Web Forms deprecated? It has no upgrade path to .NET (Core) from .NET Framework. Are you going to add a Silverlight designer too?

Don't get me wrong, I would love for such an upgrade path to exist- as I have old web apps in Web Forms that I have no interest in totally rewriting just to get them on modern cross-platform .NET. WYSIWYG is a lost art in modern frameworks.

If your telemetry shows there are a lot of Web Forms apps out there still in development, then please talk to the .NET team and get an official migration path. It's crazy the VS team is investing in Web Forms while the .NET team officially abandoned it years ago.

Here's the point-by-point response from Sayed Hashimi from the Visual Studio dev team:

Hello MgSam, thanks for the comment.

I'm confused about why you guys are investing in Web Forms tooling. Isn't Web Forms deprecated?

Web Forms is NOT deprecated, the framework support is limited to critical updates, but all ASP.NET full .NET Framework projects are fully supported. While we are not investing in the Web Forms framework, we still need to ensure that Web Forms developers can successfully develop their apps in Visual Studio.

Are you going to add a Silverlight designer too?

In contrast to Web Forms, Silverlight is obsolete so there are no investments happening there and support to develop in Visual Studio was removed years ago.

If your telemetry shows there are a lot of Web Forms apps out there still in development, then please talk to the .NET team and get an official migration path

Yes, there are LOTS of users still developing Web Forms projects in Visual Studio. Let me explain more why we are working on a new designer ("Web Live Preview"). In Visual Studio we have important accessibility requirements that we need to meet. The existing Web Forms designer is not accessible, and the code is written in a way that it's almost impossible to make it accessible. It's also not up-to-date with the latest web technology. We are creating a new designer to fix those issues. Another goal with the new designer is to one day enable a similar experience for ASP.NET Core projects (no commitments there, yet).

Please talk to the .NET team and get an official migration path

Migrating an ASP.NET full framework app to an ASP.NET Core app is very difficult, and not likely to be able to be automated in a way that will work for most users. What we are doing is working on an experiment to enable ASP.NET full framework developers to supplement the full framework app with an ASP.NET Core app. That way users can develop new pages in the ASP.NET Core project and maintain their existing full framework app. The idea is that hopefully over time more-and-more of the code base gets ported to the ASP.NET Core app. We will have more to share in this area soon. If we could create a magic wand to port an ASP.NET full framework app to ASP.NET Core we absolutely would do that, but from our investigations it doesn't seem feasible.

Another thing that we are doing with Web Live Preview is integrating the Edge Developer Tools into Visual Studio. We have an extension at https://aka.ms/edgetools-for-vs. We are hoping to get this built into Visual Studio in an upcoming release. I say this so that you know that the investment we are making in Web Live Preview is not strictly limited to ASP.NET full framework apps, there is value coming soon for ASP.NET Core users as well.

Thanks for your comment, I really appreciate it. Please let me know if you have any more questions.

The part of the announcement post that triggered the comment was this:

"In the initial release of Visual Studio 2022 we introduced a new capability for those working with Web Forms applications and the designer. Web Live Preview enables your running app to be the design surface and provides code synchronization across source and web surface to help you navigate directly to the code file for the element you are editing.

After continued studies of developers with Web Forms apps, we have improved the experiences even more in this release. We have also worked with several ASP.NET control vendors to ensure their support in this new designer. If you are working in Web Forms, please switch to this feature using Tools > Options > Web Forms Designer options menu and continue to give us feedback!

Note that some efforts have been made to automate Web Forms conversions, notably a project from Mobilize.Net as explained in last year's article: "Firm Automates Legacy Web Forms-to-ASP.NET Core Conversions."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube