Should I use Code-behind or Code-Inside (or Code-beside)?

Should I use Code-behind or Code-Inside (or Code-beside)?
Visual Studio .NET creates Web applications using the Code-Behind model, while Web Matrix creates them until the Code-Inside model. Visual Studio 2005 will add yet a third model (Code-beside). Which should you use? 

http://www.msdn.microsoft.com/asp.net/community/inbox/codebeside/default.aspx

Published Thursday, May 06, 2004 1:48 AM by sanjeebsarangi

Comments

Thursday, May 06, 2004 9:35 AM by Jeff

# re: Should I use Code-behind or Code-Inside (or Code-beside)?

I'm a big fan now of code-beside. I never liked inline code just because the support for it in VS sucked, but I can see a lot of use for it in cases where I need to redistribute an app (in 2005, it still sucks in 2003).
Thursday, May 06, 2004 7:10 PM by Doug Thews

# re: Should I use Code-behind or Code-Inside (or Code-beside)?

I'm also a fan of code-behind. It separates the code from the UI, and generally makes the UI portion much less messy. Plus, I can;t be sure, but I don't think that the entire section of server-side code is actually pre-compiled since it resides in the ASPX file and would be physically parsed every time. I think it might be a little slowed that way.
Tuesday, July 20, 2004 7:26 AM by Satish Sivsubramanian G

# re: Should I use Code-behind or Code-Inside (or Code-beside)?

The simple advantage of using code behind is while deploying u can simply deploy the dll's for the code behind(say c# or vb) but while deploying the .aspx with code besides ur code is visible to the production web server....

Leave a Comment

(required) 
(required) 
(optional)
(required)