Practical .NET

Switch Back to the Web Forms Editor for Static HTML

You lose some functionality with the default editor in Visual Studio 2013. Here's how to quickly switch back and get the functionality you were used to.

In Visual Studio 2013 the default editor for static HTML pages loses a lot of useful functionality compared to the default version used in Visual Studio 2012 and earlier.

In Figure 1, notice that XHTML violations such as uppercase tag names, unquoted attribute values, and attribute minimization are not shown as warnings. Also note the lack of a WYSIWYG experience option.

Default HTML Editing Experience in Visual Studio 2013
[Click on image for larger view.] Figure 1: Default HTML Editing Experience in Visual Studio 2013

To enable a better experience -- including the ability to automatically validate the mark-up, switch between validation schemas, and switch to a WYSIWYG design view -- follow these steps:

  1. In Solution Explorer, right-click any HTML file
  2. Choose Open With...
  3. Select HTML (Web Forms) Editor
  4. Click Set as Default
  5. Click OK

You'll notice in Figure 2, you get it all back.

The HTML Editing Experience Using the HTML (Web Forms) Editor
[Click on image for larger view.] Figure 1: The HTML Editing Experience Using the HTML (Web Forms) Editor

Now, that's more like it!

About the Author

Mark Price, MCT, MCSD, is a full-time trainer for UK-based Firebrand Training. He has more than 20 years of experience working in the IT and developer industry, including a two-year stint working at Microsoft. His expertise covers a number of Microsoft technologies (Azure, ASP.NET Web Forms and MVC, Web API, WCF, jQuery, C#, LINQ, Entity Framework, WPF, and Windows Store apps), HTML5, XAML, and Google developer technologies and the Google App Engine.

comments powered by Disqus

Featured

  • Microsoft's Tools to Fight Solorigate Attack Are Now Open Source

    Microsoft open sourced homegrown tools it used to check its systems for code related to the recent massive breach of supply chains that the company has named Solorigate.

  • Microsoft's Lander on Blazor Desktop: 'I Don't See a Grand Unified App Model in the Future'

    For all of the talk of unifying the disparate ecosystem of Microsoft-centric developer tooling -- using one framework for apps of all types on all platforms -- Blazor Desktop is not the answer. There isn't one.

  • Firm Automates Legacy Web Forms-to-ASP.NET Core Conversions

    Migration technology uses the Angular web framework and Progress Kendo UI user interface elements to convert ASP.NET Web Forms client code to HTML and CSS, with application business logic converted automatically to ASP.NET Core.

  • New TypeScript 4.2 Tweaks Include Project Explainer

    Microsoft shipped TypeScript 4.2 -- the regular quarterly update to the open source programming language that improves JavaScript with static types -- with a host of tweaks including a way to explain why files are included in a project.

Upcoming Events