Move embedded C# code to seperate .CS files
Brought to you by:
ctrager
Menu
▾
▴
#430 Move embedded C# code to seperate .CS files
You should move the embedded C# code to seperate .CS files. It seperates the UI from the logic and makes things easier to read.
Everything you are doing now can also be done with codebehind .CS files so there is really no reason that I can see why you would not want to do this.
Regarding "there is really no reason that I can see why you would not want to do this"
Well, one reason is that among the fashionable developers Webforms and code-behind as the way to write your website is a technology that is on its way OUT, with ASP.NET "MVC" replacing it. Ironically, <% %> tags make their way back into the HTML with MVC technology.
Hard to keep up with fashion!
Every approach has pros and cons, and it's trying to chase tech fashion is a never-ending losing battle.
Agreed, it is hard to keep changing things based the never-ending technology changes. With MVC you still have the concept of seperating UI from code. It's just that now it's called Views and Controllers.
I too would like to see the code behind. Have considered taking the exiting code and creating the code behind myself. However my consern is that I don't want to keep it just for myself. So with that said. Would it be possible to create a branch of your code for codebehind work.