Your SlideShare is downloading. ×
Migrating to as migrating to – what should you consider
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Migrating to as migrating to – what should you consider


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Migrating to – What should you consider?There are many advantages of migrating from ASP to ASP.Net for Microsoft development- higherscalability, better language support, programmable control, increased performance, event-drivenprogramming, XML-based components, easier configuration and deployment and much more.Although migrating to ASP.NET is fairly easy, there are few difficulties that you may face during theprocess. A major problem is developers not being well -versed with .NET which may lead toproductivity decline and scaling down of performance while developers are in the process of gettingaccustomed to .NET development. Another issue that you may come across is maintaining high codequality. In ASP.NET, implementing the principles of good design is extremely difficult. So, ASP.NETapplications tend to be complex and difficult to maintain, with very low code re -use.The designers of Microsoft ASP.NET have sure done a great job in preserving backward compatibilitywith ASP applications, but there are still a few things that you need to consider before you take upASP to ASP.NET migration. Listed below are a few key consi derations that need to be taken intoaccount before migrating to ASP.NET:Co-ExistenceThe first and most important aspect that needs to be understood is the co-existence of ASP andASP.NET. Both applications can run side by side on a server as the two systems have totally separateprocessing engines. Also, separate file extensions (.asp versus .aspx) and separate configurationmodels (metabase/registry versus XML-based configuration files) are used between the twotechnologies. While relatively simple pages would migrate without any changes, more complexapplications would require some modifications.Migration StrategyFor migration, there are a number of approaches to choose from. These include:  Migrating an application for evaluation purposes  Migration of the user interface tier of a system  Migrating only specific functionality, intending that it interoperates as a part of the existing application.  Full fledge migration owing to strategic business requirementsMigration PathThe migration path needs to be chosen based on the migration strategy that you opt for. Verticalmigration is the approach used to migrate an application one tier at a time. This strategy ismost appropriate when minimal changes are required to the interfaces between applicationtiers and the application’s modules are tightly coupled.
  • 2. You should opt for horizontal migration if the application code needs to be migrated moduleby module, completing the migration for all three tiers of one module before moving on tothe next.Migration to ASP.NET needs to be carefully planned out well in advance in order to avoidany kind of hassle. Make sure you have a migration strategy in place for successfulimplementation of ASP.NET. To obtain an edge, you can create a migration team thatconsists of experienced developers and developers with .NET experience.