By Imran Salahuddin | May 5th, 2015 |
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. Most of the ASP applications are already used for daily needs and satisfactory for many users.
The question that arises is, the possibility to extend the application into .NET environment at the same time leveraging the legacy ASP code?
A complete migration to .NET can be achieved with a set of migration steps, with each step concentrating on unlocking a 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.