To Web Pages or not to Web Pages?
-
Hi! I am mostly focused on DB and desktop development, all of my "good" web stuff was done with WebForms. As my spare time allows I am slowly learning ASP.Net MVC, I agree with philosophy behind it, but learning process is much slower than expected and from time to time I look across the fence for possible shortcuts, alternatives etc. So, should Web Pages be considered as an alternative (of any sort) to ASP.Net MVC? Do you consider it better than WebForms (and why)? Are there any important gotchas which usually aren't listed among first N Google results? Can someone share their experience? Thanks, Deka
-
Hi! I am mostly focused on DB and desktop development, all of my "good" web stuff was done with WebForms. As my spare time allows I am slowly learning ASP.Net MVC, I agree with philosophy behind it, but learning process is much slower than expected and from time to time I look across the fence for possible shortcuts, alternatives etc. So, should Web Pages be considered as an alternative (of any sort) to ASP.Net MVC? Do you consider it better than WebForms (and why)? Are there any important gotchas which usually aren't listed among first N Google results? Can someone share their experience? Thanks, Deka
I have worked on Webforms previously and now MVC. In my opinion MVC is better in performance, speed and flexible for test-driven development. Here is the interesting part.... No postbacks, No viewstates, No server controls, No page life-cycle. All done with HTTP RESTful services and HTML controls. And it's completely stateless. Controller controls all user interactions. each user request is served by raising an action method in the controller. Bundling, routing and Web API's are some of the interesting areas in ASP.NET MVC Check this MSDN articel[^]
- Regards -
J O N -
Hi! I am mostly focused on DB and desktop development, all of my "good" web stuff was done with WebForms. As my spare time allows I am slowly learning ASP.Net MVC, I agree with philosophy behind it, but learning process is much slower than expected and from time to time I look across the fence for possible shortcuts, alternatives etc. So, should Web Pages be considered as an alternative (of any sort) to ASP.Net MVC? Do you consider it better than WebForms (and why)? Are there any important gotchas which usually aren't listed among first N Google results? Can someone share their experience? Thanks, Deka
Have a look at a response I posted to a similar question Asp.net MVC VS Asp.Net[^] In my opinion, MVC is a far better pattern to use for web development - once you get your head around the initial learning curve, it all becomes pretty simple :)
-
I have worked on Webforms previously and now MVC. In my opinion MVC is better in performance, speed and flexible for test-driven development. Here is the interesting part.... No postbacks, No viewstates, No server controls, No page life-cycle. All done with HTTP RESTful services and HTML controls. And it's completely stateless. Controller controls all user interactions. each user request is served by raising an action method in the controller. Bundling, routing and Web API's are some of the interesting areas in ASP.NET MVC Check this MSDN articel[^]
- Regards -
J O NOk, I agree, but you haven't answered my question. Web Pages, are they worth it?
-
Ok, I agree, but you haven't answered my question. Web Pages, are they worth it?
-
Have a look at a response I posted to a similar question Asp.net MVC VS Asp.Net[^] In my opinion, MVC is a far better pattern to use for web development - once you get your head around the initial learning curve, it all becomes pretty simple :)
Yeah. To bad about legacy apps you cannot have time and resources to port to MVC :sigh:
No more Mister Nice Guy... >: |