XHTML validation and asp.net

When I run the xhtml validator in Dreamweaver 8, it shows all the asp.net tags
as invalid. Now I know that asp.net tags are not valid xhtml tags, but
Dreamweaver should reconize that these are server-side tags, shouldn't it?
Otherwise, a typical page will show numerous validation errors.

Any know work around for this?

Thanks,
Brett

When I run the xhtml validator in Dreamweaver 8, it shows all the asp.net
tags
as invalid. Now I know that asp.net tags are not valid xhtml tags, but
Dreamweaver should reconize that these are server-side tags, shouldn't it?

You'd think so. Is your page extension .aspx?

If not, just validate the page from the server...which you should do
anyways, since the markup that matters is the markup that comes AFTER the
page is pre-processed by the server.

-Darrel

Yep, it's an .aspx page. Validating on the server-side is fine, I just found
it a bit annoying that the built-in validator can't recognize server tags and
ignore them. Is it just me?

Oh well.

Thanks,
Brett

..oO(brettmckinney)

Yep, it's an .aspx page. Validating on the server-side is fine, I just found
it a bit annoying that the built-in validator can't recognize server tags and
ignore them. Is it just me?

Probably. What if all the HTML in a page is generated by a script and DW
ignores these "server tags" - what would be left for validation? If you
use scripting then these scripts _must_ be executed before validating
their output.

Micha

brettmckinney wrote:

Yep, it's an .aspx page. Validating on the server-side is fine, I just found
it a bit annoying that the built-in validator can't recognize server tags and
ignore them. Is it just me?

Built in validators are almost useless. They use computer resources
(slows down Dreamweaver) and are highly inaccurate. Better to use a
validator AFTER the page is served.

--
Tom Muck
http://www.tom-muck.com/