Though, i'm still a novice for ASP.NET MVC, my manager asked me for a report about ASP.NET MVC's productivity. Actually we are planning to develop a real life, kinda big system using ASP.NET MVC. The questions are:
1- Is it really goona scale for a fairly large system?
2- Is it goona be easy for developers to pick up in a short period "weeks"?
3- Are there any real life systems that are built using ASP.NET MVC? "Except for NerdDinner"
4- How can MVC save some developing time over ASP.NET?
MVC provides better support to TDD (Test driven development). TDD is related to the test first programming concepts of extreme programming. It helps us to reduced time in reworks and helps create loosely coupled code. MVC enforces separation that reduces complexity of project structure.
The ASP.NET MVC framework offers the following advantages: It makes it easier to manage complexity by dividing an application into the model, the view, and the controller. It does not use view state or server-based forms.
The simple answer is that by loading just the necessary content, the MVC page results in better responsiveness AND higher Google page speed score. And that naturally leads us to the next topic: search engine optimization.
If by productivity your manager really means "how long will it take to write feature X?" then quite possibly you will not be as productive in the short term with ASP.NET MVC. However, the much better seperation of concerns in the framework, when compared to webforms, means it is much easier to test and write well structured code for.
This will give you improved long term productivity but probably at the expense of short term productivity. If you can get your manager to see past this then you're on to a winner. Good luck with that one!
To answer your direct questions:
To answer #3 - yes, you're using one right now :o) What Was Stack Overflow Built With?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With