ASP.NET MVC is a new technology in comparison with many other Web development technologies available, especially those produced by Microsoft, so it looks like there will be a great demand for ASP.NET MVC in the coming years, and many companies will switch to the technology. At the moment, several enterprise applications that are built with ASP.NET WebForms require an implementation of the MVC pattern to perform better. The advent of ASP.NET MVC provides a good opportunity for companies to migrate their applications to ASP.NET MVC and enjoy its flexibility and testability features.
Besides, there should be a next generation of Web applications built with ASP.NET MVC rather than ASP.NET WebForms. There is a lot of excitement in the community about the idea of building future applications with this framework because it has some unique features that are not available in ASP.NET WebForms. We have already discussed the advantages of ASP.NET MVC over ASP.NET WebForms, particularly in Chapter 2 (as well as some advantages that ASP.NET WebForms have).
Though it is best to make a clear decision to use ASP.NET MVC or its alternatives before implementing a project, at times developers will want to migrate their existing projects from ASP.NET WebForms to ASP.NET MVC. This strongly depends on the type of project and its requirements, and no one can invent a step-by-step guide that would be consistently reliable for migrating all applications.
The purpose ...