Richard, I agree. Code-behind is perfect for separating design from content, and is much more manageable than the classic-ASP approach.
However, the compile-first approach means we'll need to see a move from ASP pages being produced by designers (HomeSite/Dreamweaver etc.) back to pages having to be produced by developers (VS.NET) Not sure how wise this is... I've got better things to do that glue ASP and HTML pages together. -----Original Message----- From: Richard Birkby [mailto:[EMAIL PROTECTED]] Sent: 12 April 2002 17:01 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Disable generation of code behind in IDE Why does everyone suddenly want to move away from code-behind? First there's an MSDN chat about it, and now an IDE which supports it. I know that Code-Behind is unnatural for classic-ASP developers due to it's compile-first mentality, but has everyone but me decided it's a Bad Idea?. Richard > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of > Farhan > Sent: 12 April 2002 16:52 > To: [EMAIL PROTECTED] > Subject: [DOTNET] Disable generation of code behind in IDE > > > is there anyway to disable code behind generation in VS IDE? > > Thanks, > Farhan > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
