Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 02, 2009 04:42 PM by vpmragu
Sep 29, 2005 05:51 PM|LINK
Sep 30, 2005 03:07 PM|LINK
In v2, Microsoft have gone with XHTML 1.0 Transitional as the default doctype on pages. In v1.1, the default doctype was HTML 4.0 Transitional.
As you've no-doubt guessed, you're now working with a much more strict standard. So you have 2 options:
You can also read more about doctypes at the
w3 schools site.
Regarding the temporary code, this is part of the "on-the-fly" compiling of the v2 framework. If you find that you're getting errors in there, sometimes it helps to manually delete all the files in that temporary directory. You'll be best to run IISRESET
before you do that, though.
Sep 30, 2005 09:12 PM|LINK
Oct 12, 2005 02:57 PM|LINK
Dec 07, 2005 06:28 PM|LINK
The quickest way to get rid of the build errors is to turn off validation, which is on by default. In Visual Studio 2005, with your project open if you only want to affect one project, go to menu option Tools then Options.
In the Options dialog navigate to Text Editor, HTML, Validation. Uncheck the Show Errors option for your target browser. Build again and you won't see the validation errors.[H]
awesome! i needed that... thanks...
Dec 16, 2005 09:34 PM|LINK
The Visual Web Developer designer doesn't directly use the <!DOCTYPE ... > element at the top of the page for design-time validation -- that's just the way you advertise which language the page was written in to the browsers/search bots/etc. that request
the page. The validation target used for the validation errors you asked about is actually found in a dropdown in the "HTML Source Editing" toolbar that should be visible by default when editing an ASPX page in Source View. You could turn validation off
entirely, but you generally should pay attention to these errors since they make it harder to machine-parse your content.
Feb 13, 2006 06:54 PM|LINK
Feb 22, 2006 02:07 PM|LINK
In general, I find the strict validation useful, but is there a way to customize what gets (or more importantly: doesn't get) flagged? Not something general like, "when client tags are not lowercase" inside tools->options but something specific...
The web stats package I use needs a non-standard attribute stats="1" added inside the
<body> tag for any page I need kept track. So for the hundreds of pages on the site, this validation error spams the error list:
Attribute 'stats' is not a valid attribute of the element 'body'.
How do I configure VS or at least the project to ignore this (and other) specific "errors" so I don't have to turn off the error list entirely?
Apr 24, 2007 04:06 PM|LINK
Instead you can add
which almost eliminates your problem. bcoz i did this way only i got out of the problem.
Oct 16, 2008 06:53 PM|LINK
Thanks. It really solved the error.