Migrating to ASP.net – What should you consider? by gangulypoushali

VIEWS: 28 PAGES: 2

More Info
									Migrating to ASP.net – What should you consider?

There are many advantages of migrating from ASP to ASP.Net for Microsoft development- higher
scalability, better language support, programmable control, increased performance, event-driven
programming, 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 the
process. A major problem is developers not being well -versed with .NET which may lead to
productivity decline and scaling down of performance while developers are in the process of getting
accustomed to .NET development. Another issue that you may come across is maintaining high code
quality. In ASP.NET, implementing the principles of good design is extremely difficult. So, ASP.NET
applications 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 compatibility
with ASP applications, but there are still a few things that you need to consider before you take up
ASP to ASP.NET migration. Listed below are a few key consi derations that need to be taken into
account before migrating to ASP.NET:

Co-Existence
The first and most important aspect that needs to be understood is the co-existence of ASP and
ASP.NET. Both applications can run side by side on a server as the two systems have totally separate
processing engines. Also, separate file extensions (.asp versus .aspx) and separate configuration
models (metabase/registry versus XML-based configuration files) are used between the two
technologies. While relatively simple pages would migrate without any changes, more complex
applications would require some modifications.

Migration Strategy

For 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 requirements


Migration Path
The migration path needs to be chosen based on the migration strategy that you opt for. Vertical
migration is the approach used to migrate an application one tier at a time. This strategy is
most appropriate when minimal changes are required to the interfaces between application
tiers and the application’s modules are tightly coupled.
You should opt for horizontal migration if the application code needs to be migrated module
by module, completing the migration for all three tiers of one module before moving on to
the next.

Migration to ASP.NET needs to be carefully planned out well in advance in order to avoid
any kind of hassle. Make sure you have a migration strategy in place for successful
implementation of ASP.NET. To obtain an edge, you can create a migration team that
consists of experienced developers and developers with .NET experience.

								
To top