Programming Microsoft ASP.NET MVC

Technically speaking, ASP.NET MVC is far superior to Web Forms. This is because it’s newer and was designed around an alternate and more modern set of principles and patterns. Is this sufficient reason for you to switch to it? In my opinion, it isn’t. ASP.NET MVC is an excellent choice from the perspective of developers, but that fact alone doesn’t automatically translate into a tangible benefit for the customer and the project. Moreover, ASP.NET MVC is much less forgiving than Web Forms and requires training, or at least self-training.
In 10 years of using Web Forms, I’ve seen many professionals with limited programming skills produce effective Web front ends using data-bound controls and a bit of Microsoft Visual Basic. This will not happen with ASP.NET MVC. Worse yet, if you start writing ASP.NET MVC code taking the learn-as-you-go approach that worked for many with Web Forms, you will surely cook up great examples of much hated spaghetti code.
So learning ASP.NET MVC makes you a better developer, but it has a cost. Who’s supposed to pay for that? Your customer? Your company? You, yourself? How would you justify to a project manager the extra training costs for just using ASP.NET MVC? You can try, but the natural objection is this: “OK, but where’s my return? Can’t we take this project home by simply using Web Forms, which we already know through and through?”