A couple of days ago Scott Guthrie posted about HTML validation checking feature in Visual Studio 2005:
"...The reason we are now surfacing HTML validation issues in the error list by default is that we are trying to promote more standards-based HTML with VS 2005 and ASP.NET 2.0, as well as to catch potential rendering and browser functionality errors earlier in the development process (so that you dont have to run and carefully analyze every page in your app. looking for these types of issues).
...If youd rather not have these types of HTML validation errors show up in your error-list, you can disable this functionality by selecting the Tools->Options menu item in VS or Visual Web Developer."
The fact is that many developers are unhappy about this feature. For example Rick Strahl explains several issues regarding HTML validation:
"...So there are two issues here: First the fact that HTML format errors really have no business being flagged as errors. Errors in this environment should only be things that break the build and HTML errors don't qualify in my book. I can appreciate the folks who are Nazis about their HTML Validation and want to see them prominently, but having them show as errors doesn't do anything other than display here its not breaking the build, so this is purely an annoying and non-configurable GUI feature."
...The other is that of context. If I compile an individual assembly, that has nothing to do with HTML markup tags why should the IDE show these errors in this place its completely out of context. Theres no options to have VS show the difference between background compile/eval errors of whats open and what compile you just ran. All this stuff just gets jumbled together into a single bin."
I agree. Half a year ago I posted a bug on compiler errors in xhtml about inconsistent behavior and conversion issues. It was resolved by design:
"Thank you for your feedback. After Beta 2, we changed XHTML conformance to Transitional for all new Whidbey applications. Unfortunately, this triggers an issue when converting a VS03 web project. A number of developers wrote script that relied on the id attribute of the Form tag (it was the most common breaking change for ASP.NET in compatibility labs around the worlds) . This is a not allowed attribute in transitional -- so if we make it transitional on upgrade scenarios we break a lot of developer client side script. So when we convert a VS03 web project we set XHTML conformance to use Legacy mode."
What do you think ?
Saturday, November 26, 2005 5:57 PM