filmov
tv
5 ASP to ASP.Net Migration tips for any business
Показать описание
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.
Side-By-Side Approach
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.
Local Migration
Local migration is the migration of a joined part of one of the legacy application layers. Fundamental layers' code, closely joined with this part, can also be migrated. In general, it will be a migration of some part of a business layer, with a matching data layer part.
Rewrite/optimization
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.
Client-based synchronization approach
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
Dynamic synchronization must be used if a substantial amount of pages update the state. Please remember that there are no performance gains because the state has to be synchronized frequently. Dynamic synchronization should occur automatically on loading and unloading every page, giving you the freedom from having to add synchronization code physically.
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!
This leads us to our first tip in an ASP to .Net migration.
Side-By-Side Approach
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.
Local Migration
Local migration is the migration of a joined part of one of the legacy application layers. Fundamental layers' code, closely joined with this part, can also be migrated. In general, it will be a migration of some part of a business layer, with a matching data layer part.
Rewrite/optimization
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.
Client-based synchronization approach
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
Dynamic synchronization must be used if a substantial amount of pages update the state. Please remember that there are no performance gains because the state has to be synchronized frequently. Dynamic synchronization should occur automatically on loading and unloading every page, giving you the freedom from having to add synchronization code physically.
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!