Hi,

Is it just me or is it impossible to generate valid HTML code with
Visual Studio 2003 .net? I am specially thinking about the
DropDropList. When rendered it puts a language="javascript" attribute
in the select. That is one example of an invalid tag attribute.

What can I do to ensure valid html (preferable xhtml)?
_Can_ I do something?

--
Thomas Due
Software Developer
Scanvaegt Nordic A/S

I'm using XHTML 1 transitional -- it's doable, but one has to do some =
rewriting; I tried for strict for a while and gave up -- too many =
controls just couldn't be convinced to not sprinkle extra bits I didn't =
want, and I didn't have time/money to rewrite the entire control =
library.

The biggest problem I ran into was the HTML editor/designer rewriting =
my HTML (like taking all of <img /> and turning them into <img> etc.) If =
you beat on it long enough you can get it to stop most of this --

If you really want to use XHTML, I think there's a company selling =
XHTML controls for ASP.NET, I've never tried them; do a google. I'm sure =
(hope) Whidbey will be better able to generate standard markup. I think =
there's an intellisense on the web for XHTML for Visual Studio -- yet =
another google -- that is helpful.

Good luck.
[quoted text, click to view]
Hi,

Is it just me or is it impossible to generate valid HTML code with
Visual Studio 2003 .net? I am specially thinking about the
DropDropList. When rendered it puts a language=3D"javascript" =
attribute
in the select. That is one example of an invalid tag attribute.

What can I do to ensure valid html (preferable xhtml)?
_Can_ I do something?

--=20
Thomas Due
Software Developer
Scanvaegt Nordic A/S

another big problem is aps.nets use of underscore in system ID tags.=20

-- bruce (sqlwork.com)



[quoted text, click to view]

I'm using XHTML 1 transitional -- it's doable, but one has to do some =
rewriting; I tried for strict for a while and gave up -- too many =
controls just couldn't be convinced to not sprinkle extra bits I didn't =
want, and I didn't have time/money to rewrite the entire control =
library.

The biggest problem I ran into was the HTML editor/designer rewriting =
my HTML (like taking all of <img /> and turning them into <img> etc.) If =
you beat on it long enough you can get it to stop most of this --

If you really want to use XHTML, I think there's a company selling =
XHTML controls for ASP.NET, I've never tried them; do a google. I'm sure =
(hope) Whidbey will be better able to generate standard markup. I think =
there's an intellisense on the web for XHTML for Visual Studio -- yet =
another google -- that is helpful.

Good luck.
[quoted text, click to view]
Hi,

Is it just me or is it impossible to generate valid HTML code with
Visual Studio 2003 .net? I am specially thinking about the
DropDropList. When rendered it puts a language=3D"javascript" =
attribute
in the select. That is one example of an invalid tag attribute.

What can I do to ensure valid html (preferable xhtml)?
_Can_ I do something?

--=20
Thomas Due
Software Developer
Scanvaegt Nordic A/S