Hi,
I've been working with .Net since the very early days, and yes it
does have it's frustrations initially to get sites to validate,
however there is no reason why it can't be done. With .Net 1.1 we
wrote a PageFiltering module which did a small amount of manipulation
to the generated HTML to make it validate, however the class is no
more than about 100 lines long. The only control we had to "fix" was
the RadioButton, so that it could handle the group attribute.
In regards to Visual Studio changing the markup. Firstly you can
change your VS.Net preferences to stop capitalisation etc, also I'd
recommend you never switch Design mode, you really should never need
to anyway.
Examples that do validate can be found at http://www.sjplaw.co.uk
[1]and http://www.white-agency.co.uk [2] . Please bear in mind these
is a content managed site, so the copywriters may have stopped some of
the pages validating.
Another example site that validates to XHTML 1.1 -
http://www.eastyorkshireclassic.co.uk/nationals [3]
As a development studio we have recently switched to the Castle
MonoRail Framework, so we no longer have any issues at all making
pages validate. To be honest WebForms are a poor technology and any
self respecting web developer should be using the available MVC
frameworks. You have to remember that WebForms were created for VB
developers who were used to drag and drop GUI building and don't care
about web standards, let alone really understand what it means. (I may
be generalising here a bit, but I'm right in most cases).
John Polling
Senior Web Developer
White Agency
Links:
------
[1] http://www.sjplaw.co.uk/
[2] http://www.white-agency.co.uk/
[3] http://www.eastyorkshireclassic.co.uk/nationals
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
