E-mail List Archives
Re: Visual Studio.Net 2003 and accessibility
From: Christian Heilmann
Date: Mar 17, 2006 9:00AM
- Next message: Karl Dawson: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message: Austin, Darrel: "RE: Visual Studio.Net 2003 and accessibility"
- Next message in Thread: Karl Dawson: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message in Thread: Austin, Darrel: "RE: Visual Studio.Net 2003 and accessibility"
- View all messages in this Thread
> In addition, in .net 1.1, a lot of the built-in controls spit out pretty
> bad markup. As such, I've resorted to writing a lot of my own controls
> that manually build the HTML. Kind of defeats the purpose of .net, but
> was the only way to get control over my output.
>
> Supposedly, asp.net 2.0 as well as the Visual Studio 2005 product line
> fix a lot of these issues.
Yes and no. I've attended a course on VS2005, and it does produce
better code and also allows for templating like dreamweaver does
rather than creating lots of small includes. However, the developer
once again has too many options to mess things up. VS.NET is a typical
IDE that assumes the developer knows everything while normally that is
never the case.
--
Chris Heilmann
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
Binaries: http://www.onlinetools.org/
- Next message: Karl Dawson: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message: Austin, Darrel: "RE: Visual Studio.Net 2003 and accessibility"
- Next message in Thread: Karl Dawson: "Re: Visual Studio.Net 2003 and accessibility"
- Previous message in Thread: Austin, Darrel: "RE: Visual Studio.Net 2003 and accessibility"
- View all messages in this Thread