« Professional JSP 2.0... | Main | Westword Music Showc... »
20030620 Friday June 20, 2003

.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! wink Posted in Java at Jun 20 2003, 01:14:42 PM MDT 3 Comments

Comments:

My background is with J2EE. All things being equal, I'd use J2EE over .NET every single time. However, the one thing that .NET has is Visual Studio .NET. Being able to drag and drop components that generate ASP.NET (with code behind) is not particularly useful for me, but it is for a different class of developer (the "corporate developer" often discussed at this year's JavaOne). Unfortunately, the J2EE IDE vendors are simply not there yet.

Posted by Ted on June 20, 2003 at 02:25 PM MDT #

Obviously Ted has not used java code genrationtools yet such as xdoclet and etc..and to be blunt lets not repeat Sun's msitake in code generation by visual tools tha tproduces code tha tyou cannot edit as evident in SuneoNe studio GUI designer! But the strength in choosing J2ee for web services is that you have achoice of vendors for those web services libraries and thus make an informed choice of who matches the standards closer than anyone else!

Posted by Fred Grott on June 20, 2003 at 03: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 02:28 PM MDT #

Post a Comment:
  • HTML Syntax: Allowed
Click me to subscribe
Matt Raible is a Web Architect who enjoys developing applications with open source technologies. Contact me for rates.
« January 2009
SunMonTueWedThuFriSat
    
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
       
Today

Recent Entries

Tag Cloud

abbie acegi appfuse denver grails gwt hibernate jack java jsf linkedin maven myfaces oscon rails skiing spring springmvc stripes struts struts2 tapestry travel webframeworks wicket