I have recently developed my first web site using MVC. I think it is a good thing to have in your toolkit but falls very short of meeting all requirements.
I think if you need a simple to moderately complex user interface with a SQL backend. MVC is a good choice.
For websites where clients need functionality similar to that offered by a Windows Forms application, ASP.Net is your best choice.
I liked the overall MVC pattern. The frustrating bits are:
- Some appreciable loss of functionality compared with ASP.Net when using third party MVC controls. I realize that some developers think MVC controls and events are bad - but I will bet you that very few of them have ever had to sweat a payroll. Telling a client "it's MVC" doesn't exactly make them leap with joy towards their checkbook.
- Things that should be straightforward, such as opening a view in a new browser window (not a pop-up), seem to be complete mysteries.
- The "magic" naming scheme with Views and Controllers is annoying. I honestly would like to see full class names in MVC calls.
In short, I will use MVC again; but only where it meets the requirements of the job.
View Complete Post