The Ultimate ASP migration Strategy

Making a suitable ASP migration strategy is not always cut and dry. Most probably would be tempted to rewrite the entire web application in Microsoft .NET from scratch. However, management might not be as enthusiastic as a developer is to this idea. The application is already in production and satisfies the requirements. My question would be, why follow a more risky and costly path if it is possible to start extending the application in .NET and at the same time preserving an investment in the legacy ASP code?

Specifically if a complete ASP migration can be reached progressively in a number of evolutionary migration steps, with every step resolving a concrete migration-justifiable problem.

In any ASP migration it is important to stress that even with a discreet "do not touch legacy code" strategy; some changes to this code must be done. A few that I have found are:

1) Unexpected small future updates that are tightly coupled with legacy code and are preferred, compared to the code migration option.
2) Modifications determined by the decision to access .NET code from legacy code.
3) A legacy code update for ASP and ASP.NET state synchronization.
4) Variations driven by the choice to expose legacy code to .NET code.

An ASP migration to .Net is a platform to build a better product. The three main advantages of ASP.net are effortlessness of development, better efficiency with master pages and the availability as well as security of the source code.

With an ASP migration to .NET it will help you achieve better performance, higher scalability and improved agility.

ASP Migration will allow you to work on a flexible stage and will enable product enhancements at later stages. If you want to build a robust and well-architected software product using the ASP.Net framework, the time is now!

To learn more about the ultimate ASP migration strategy, watch my video blog.