Well the thing is code behind is a much better model for web application design, but also more cumbersome for just a quick dynamic page. I tend to dislike IDE's that force coding styles on you without a choice, this is why I gave up on Frontpage along time ago when it mutilated hand coded html to its own satisfaction. Main point is, it nice that VS.Net automates code behind for you but ASP.Net can do without it perfectly fine and we should be able to write code in that manner, if its our choice.
Justin -----Original Message----- From: Richard Birkby [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 12:01 PM 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.
