Compiled Fast, Conventional slow
Pretty much answers it.
Code behind is better for the developer, end-user and seller:
1.) Apps built with code-behind can be distributed as DLLs - hence your application is protected and your code encapsulated.
2.) For graphic developers and programmers the code/graphics are split up for the most part. Hence your graphic guru will not overwrite your 400 line class file that makes a mokey shoot fruit out of his butt.
3.) If programmed correctly the code should be separed into regions which makes the code very easy to read/troubleshoot/add. Yes that only works for VS developers, but hey, its worth using just for the regions.... An example is attached..... This is an actual suite of applications that I wrote. (sorry for the format, it was done quickly)
4.) Logically it DOES NOT SLOW down the process and in some cases will speed it up. To really see how effecient your code is you will need to test it, and also look at the MSIL code that is created from your app.
5.) Normal asp programming makes much greater sense, UNTIL you learn .net -- you will find yourself saying "oh, thats how you do that, or why didnt they just call it THIS and I would have known what they meant." - it all has to do with mindset. MS is trying to re-program you. In the long term you will see the benefits, and you will see similiarities when working with other O/S and apps.
Hence:
Object
Context
Container
Since Win98 for example, everyting is object based. Did you notice that when you opened the explorer that it used to say "14 folders and 344 files"? -- Now it will say "14 objects" or "344 objects"
---------------------------------------------------
:-\
