>> * Don't use postback. Just give up, it's a badly implemented hack to
maintain state in a webpage misusing forms and introducing complete
JavaScript dependence. Just because Visual Studio makes it very easy
to accidentally use it, doesn't make it ok. Just pretend it was never
there.
Do you mean
>> Avoid using the pre-wrapped ASP.NET controls. DataGrids aren't so
bad, but you get much more mark-up control by using a Repeater.
Similarly, rather than using an asp:label, there's a mark-upless version
that doesn't insert elements. I forget the name, sorry, but it
does exist.
I think Ben migh
A few tips based on my experience of working with ASP.NET 1.1:
* First up, consider sticking to an HTML 4 DOCTYPE. It's really not as
big a deal as some advocates would have you think ;-) - Critically, if
you try and force it to use XHTML and someone accidentally clicks
'Design View' your code is
l the best!
Rachel
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Wayne Douglas
Sent: Wednesday, 9 November 2005 9:12 a.m.
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Standards and .NET
http://www.codeproject.com/aspnet/ASPNET2XHTML.asp
VS2005 d
http://www.codeproject.com/aspnet/ASPNET2XHTML.asp
VS2005 drastically improves this situ.
hth
:]
w
Chris Kennon wrote:
Hi,
Yesterday I spoke with you all regarding issues with using CSS and
.NET. Below is the site underdevelopment. I'm told div's are casuing a
problem, in addition to
