Windows Azure and ASP.NET MVC Migration

Chapter 1

Migrating from ASP.NET to ASP.NET MVC 4

CONCEPTS

IN THIS CHAPTER

• Knowing what you need to start
• Understanding the difference between ASP.NET and ASP.NET MVC
• Seeing the differences between ADO.NET and NHibernate
• Exploring the improvements from IIS 7.0/7.5/8 to IIS 6
• Understanding Team Foundation Server
• Using Test Driven Development in ASP.NET MVC

Deciding to take the leap from one technology to another is a difficult one. You face the risk of improper implementation of the technology, which can cause performance issues. You also face possible impact to business logic, which can produce disruption to your customers and partners. Many core business processes were written many years ago and live on legacy environments; although the developers who wrote them are long gone, and the support teams who run the operations likely are offshore and have a high resource turnover rate. Over time, the cost of maintaining these legacy systems will increase, and the knowledge of how they work will continue to dwindle.

Although change from legacy systems to more robust platforms and newer technologies is difficult, the rewards in the form of cheaper operations cost and increased customer loyalty, as well as avoidance of risks, likely setbacks, and wrong turns are worth the effort. Not only that, but your employees will stay around longer and your developers will be happier because they get exposure to and are working on the newest technologies.

After you decided to migrate for all those ...