By Ghulam Nabi Shah | March 17th, 2015 |
When it comes to ASP to ASP.NET migration, legacy code can be migrated gradually, while applying migration strategies, and running legacy code for a long period of time until a complete migration is achieved.
This leads us to our first tip in an ASP to .NET migration.
The notion of the side-by-side approach depends on on the hypothesis that legacy code and .NET code implement different parts of the application with low coupling between them.
Understanding that local migration by definition is the migration of a united part of one or more of the legacy application layers.
The rewrite/optimization can be done after an ASP to .NET migration, in parallel with it or instead of it. This allows .NET benefits as: layered application architecture, caching, separation of HTML views from code behind, server controls and data binding, server events, view state, the .NET exception handling, improved developer productivity, improved maintainability, and so on.
This approach can be implemented by developing two intermediate pages that will sit between ASP and ASP.NET pages involved in client-based synchronization.
Dynamic synchronization should only be used if a considerable amount of pages update the state. Never forget, there will be no performance gain because the state has to be harmonized habitually.
ASP to ASP .NET Migration ranges from local to complete migration of the application as a whole. Different approaches can be useful at different phases of this migration procedure, ending with a whole migration or the end of application support, whichever comes first.
If you are looking for more ASP to ASP.NET migration tips, get free access to my video blogs from here!
