Enforcing XHTML Compliance in ASP.NET Applications
Having spent the last few years working on government projects where the use of xhtml was required, it was very frustrating for me, and the project teams, that asp.net did not support the standard. You might argue that the asp.net environment is a visual ide where you drop your controls and, as Don Box put it at a conference a couple of years ago “let .net and let go” of the output. Even so, if you want to use asp.net on standards compliant projects – and I certainly do – something has to be done until (or if) vs.net more fully supports xhtml. So I had high hopes for this ‘eBook’.
Alas, it’s way more optimistic than I am about vs.net and xhtml, it doesn’t present real world problems, and whilst it’s true that we can always write our controls to produce xhtml output, it doesnt really address the issue. Has this person ever even run a simple aspx page through a validator? I think not. And writing a filter to ensure that the resulting output is valid xml is missing the point altogether. Finally the ‘eBook’ is really only an article from asptoday – it’s simply not worth the money.
