Can someone point me to some places where I can find the pros and cons of using code behind in development. Like I know code behind uses more system resources then putting the code right on the aspx page. Can anyone send me some links on this subject.
More of an organization technique. Both ways will work, as i started without, and i am now using codebehinds. I would think it helps designate your classes calling your dlls and namespaces as needed.
Using code behind also helps you as a .NET developer because it makes the jump from web applications to desktop application seamless (with the exception of some different presentation-namespace classes of course, but even then...).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.