.NET's built-in tools and controls generate invalid XHTML and CSS
Mails we've received, forum discussions, and recent Splorp posts
all complain that .NET's built-in tools and controls generate invalid
XHTML and CSS. The workaround? Don't use the built-in tools and
controls. The value of .NET without those built-in tools and controls?
Not much.
.NET is Microsoft's platform for web services. It derives it power
from XML, a web standard. A product based on one open standard should
support others, not break them.
When Microsoft does the wrong thing, developers feel helpless. You
are not helpless. You have a choice of development platforms. [Zeldman]
(emphasis mine) The choice is simple, use J2EE ~ where the flexibility is free!
Posted by Ted on June 20, 2003 at 08:25 PM MDT #
Posted by Fred Grott on June 20, 2003 at 09:41 PM MDT #
> You have a choice of development platforms.
Sometimes you don't have a choice. I, like Zeldman, am a front-end guy working with back-end coders. The technology decisions behind the devlopment platform have already been made and laid down. My job is to work with that choice, not fight against it because it doesn't do this or doesn't do that. If the development platform decision had been up to me (and providing I actually had enough application background to make such a decision) I probably have chosen differently. That isn't the case, so my goals have changed. I want to find a way to make the current .Net system more compliant. Maybe not perfect, but more compliant.
Thanks for the mention, regardless. Cheers.
Posted by Grant Hutchinson on June 23, 2003 at 08:28 PM MDT #