Apr 11, 2011
One main benefit of ASP.NET MVC is that you can easily and quickly write RESTful implemenations. Also, ASP.NET lends itself more towards pure browser coding of controls and usage of jQuery, true seperation of concerns. Things are more cumbersome with the old ASP.NET server controls.
Apr 22, 2011
Your question depends whether you're contemplating a move from WebForms ASP.NET to ASP.NET MVC or making a choice between the two if you're starting with ASP.NET.
If you're starting go with MVC. If you're a seasoned WebForms developer and maintaining current WebForms apps, stay with WebForms. Converting apps is time consuming, error prone and time could be used to add/enhance app functionality.
WebForms is still a very viable platform. It gets better with every .NET/Visual studio version while reducing prior limitations.
If you depend on third party GUI Frameworks like from Telelrik, Infragistics, ComponentArt, DexExpress, their controls are more mature for WebForms than MVC. These controls offer high productivity, have good looking output and you don't have to worry about browser inconsistencies and bugs. They take of these issues for you. This also means you probably have less control of their html output. Something to think about if you want to spend your development time in the backend and business aspects of the app and less on the front end and GUI stuff.
Feb 21, 2013
ASP.NET and MVC are getting a little closer with each release of Visual Studio (examples include Routing, the Razor engine, and more).
I can see that over the next few years ASP.NET borrows more and more from MVC until the two are like twin sisters...
My 2 cents.
Feb 23, 2013
Who wants to have more control over things they are responsible for , well every one wants to have more and better control over things they are involved in. So whole concept of the story in our programming world is we don't want rigidity, fragility, immobility,and tight coupling What MVC brings to us is a Pattern that divides the chain of responsibilities into Model, View and Controller. But with this adaptive and flexible behavior comes the cost and time values so if the target application is a small scale one then ASP.Net is good to start with. But when the application is big and we aspect changes to be a regular visitors to our development area so we really need to separate the whole application into components and modules and create a chain of responsibilities with those components (Every Component have single responsibility ) and since all those components are self sustaining so we can even test those components without depending of any other components, thus we isolate i.e we divide then test then re-factor and eventually conquer. So the question is street fight or war, what are you getting prepared for.
Mar 08, 2011
If I were to use/learn a .Net web framework today, I would most certainly go for ASP.Net MVC mainly due to the benefits pointed out in the excellent post by Rajesh. But, if I were to choose any web framework (not limited to .Net), I would probably use Rails or Django as they seem (to me) to be far easier to work with.