Why ASP.NET MVC?
-
I just noticed that the latest version of ASP.NET MVC has just been released. I have been developing in ASP.NET for over 6 years now, my question is why should i move to MVC, What are the advantages and how about the learning curve? For those who are using it.. is it worth the investment in learning and using it? What should i watch out for? Can anyone help..
-
I just noticed that the latest version of ASP.NET MVC has just been released. I have been developing in ASP.NET for over 6 years now, my question is why should i move to MVC, What are the advantages and how about the learning curve? For those who are using it.. is it worth the investment in learning and using it? What should i watch out for? Can anyone help..
You should really google for this question. You will find A LOT of pros/cons lists and comparisons. I especially recommend the video-sessions from scott hanselman. E.g.: http://www.hanselman.com/blog/CategoryView.aspx?category=Channel9 You learn a lot and the presentation style keeps you awake easily. Often mentioned pros/cons: Pros: - Clear seperation of concerns / architecture - Programming the web as it's ment to be (there's no view-state imitating a stateful environment) - Programming the web is suddenly more fun - no weird event-handling / viewstate - Easy understandable conventions - less configuration. - Powerful architecture and tools to reuse components/views - Better support of unit-testing - Powerful Tools help you create CRUD-Szenarios with amazing speed -... Cons: - New concepts to learn, some are difficult to get used to for traditional webform-developers - Rich webform UI controls can ususally not be used in MVC - and therefor have to be replaced somehow - ... I would go the following way: - Learn the basics, whether you're planning on using MVC or not. Then you have a good start to decide if it will help you in the future (or not). This knowledge is definitely not wasted. - Have a look at the nerddinner-application from hanselman Hope this helps at least a bit