david7777
05-06-2003, 11:05 AM
I have searched the net for information on code behind - like what Visual Studio.net uses.
From what I have found, it seems that it is basically used to seperate the server code from the design. The reason to do this would be to make things neater and more easily readable.
Why do this? - To make life easier for development teams and prevent the user interface designer from messing with the server side code.
Ok, so you're not in a team, so why do it now? I guess it would be the smart thing to do in case your site becomes big enough to need a development team. Or better yet - If you use code behind as a standard, you will know how to do it when asked or when you need to :)
Are there any other advantages / disadvantages to code behind?
From what I have found, it seems that it is basically used to seperate the server code from the design. The reason to do this would be to make things neater and more easily readable.
Why do this? - To make life easier for development teams and prevent the user interface designer from messing with the server side code.
Ok, so you're not in a team, so why do it now? I guess it would be the smart thing to do in case your site becomes big enough to need a development team. Or better yet - If you use code behind as a standard, you will know how to do it when asked or when you need to :)
Are there any other advantages / disadvantages to code behind?