My one REAL frustration with Visual Studio.NET - When is XHTML going to be addressed?
It's litterally impossible to get VisualStudio.NET to produce valid XHTML if you use the Web Forms Designer. Each time you switch, ala FrontPage - you're screwed, it's messed up the meta tags. I poked around in the depths and created my own File|New Page|XHTMLDefault.aspx, even got to the point where I'd imported the XHTML DTD to Schema and tried to get Intellisense going ala FeserSoft's great XSLT intellisense in Visual Studio.NET examples. (I was SO close)
Even if you choose to forgo the Designer, when you choose to runat=server a random HtmlLiteral, you can get burnt and lose short-circuited <tags/>. Am I sequestered to using HTML 4.0 Transitional (not my 1st or 2nd choice) or am I missing something obvious?
If XML is the one true way for ASP.NET, then when will VS.NET stop getting in the way of my fabulous Zeldman-inspired XHTML/CSS creations? I have seen some of the great new ASP.NET V2 stuff, and I'm NDA'ed up the wazoo. But I'd like to hear about this issue with 1.0 and 1.1, and whatever can be said about v2. ScottGu? Anyone? Mommy?
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Comments are closed.