yemiu
November 23rd, 2004, 04:50 PM
Hello,
I ve been spending hours to read books about code behind model in .Net, and I come up with some short notes:
1. Code behind is a concept that is only valid for Web (application and service). It is .cs class (logics) in conjunction with other pages (presentation) such as .aspx or .asmx
2. the way it works in that:
+ the presentation page (.aspx or .asmx) have a reference to its code behind.
+ the presentation page contains all the GUI components. These components' names can be understod by the code behind as well. (I dont know why code behind can reference back to the presentation page)
3. Codebehind is not good when we want to use the logics to dynamically add new controls into the page because we have no idea where to put those newly added controls. We can use PlaceHolder, but it is not very dynamic. This is different from Php where we can locate in the page the code that adds the controls to the page.
Am I right? and is there anything else that I need to understand? (these notes are all that I know, no more !) . Is there any diagrams that shows the mechanics of how these things work?
Thanks
Patrick
I ve been spending hours to read books about code behind model in .Net, and I come up with some short notes:
1. Code behind is a concept that is only valid for Web (application and service). It is .cs class (logics) in conjunction with other pages (presentation) such as .aspx or .asmx
2. the way it works in that:
+ the presentation page (.aspx or .asmx) have a reference to its code behind.
+ the presentation page contains all the GUI components. These components' names can be understod by the code behind as well. (I dont know why code behind can reference back to the presentation page)
3. Codebehind is not good when we want to use the logics to dynamically add new controls into the page because we have no idea where to put those newly added controls. We can use PlaceHolder, but it is not very dynamic. This is different from Php where we can locate in the page the code that adds the controls to the page.
Am I right? and is there anything else that I need to understand? (these notes are all that I know, no more !) . Is there any diagrams that shows the mechanics of how these things work?
Thanks
Patrick