Last post Oct 26, 2010 08:47 AM by smirnov
Oct 26, 2010 08:33 AM|Nashua|LINK
I have been using ASP.net for a while now, but just as a hobby on my own.
So, I've never learned some of the more in-depth things like "Code behind".
Is it always beneficial to use it, or is it just a issue of preference?
If it is always beneficial, then does anyone have any links that point to some good training on the topic?
Oct 26, 2010 08:45 AM|MetalAsp.Net|LINK
I always use the code behind way. I prefer my html markup to be seperate from my server code. Note how I used the word "prefer". So indeed it's a preference, but I suspect the majority of people opt for the code behind way. Of course, my view may be
Oct 26, 2010 08:45 AM|muhammedsalimp|LINK
Code-behind pages offer advantages that make them suitable for Web applications with significant code or in which multiple developers are creating a Web site.
Advantages of the code-behind model include the following:
Code-behind pages offer a clean separation of the markup (user interface) and code. It is practical to have a designer working on the markup while a programmer writes code.
Code is not exposed to page designers or others who are working only with the page markup.
Code can be reused for multiple pages.
ASP.NET Web Page Code Model
Code-Behind vs. Inline Code
Oct 26, 2010 08:47 AM|smirnov|LINK