#migration path needs

There are many advantages of migrating from ASP to ASP.Net for Microsoft development- higher scalability, better language supply, programmable control, increased exercise, event-driven programming, XML-based components, easier conformation and decentralization and much more. <\p>

Although migrating to ASP.NET is fairly worth the money, there are few hard life that you may scarp during the process. A major problem is developers not being well-versed with.NET which may lead to productivity decline and disintegration down of performance season developers are in the process relative to getting accustomed upon.Net Development. Another great cause that you may come across is maintaining high code quality. In ASP.NET, implementing the principles regarding good setting is extremely difficult. So, ASP.MAKINGS applications tend against subsist complex and difficult against recruit, with very low code re-use. <\p>

The designers referring to Microsoft ASP.NET have of course done a great job in preserving wrong side out compatibility with ASP applications, exclusively there are still a few things that you need to reason the point before subconscious self take heave ASP to ASP.NET migration. Listed below are a few key considerations that poverty to be taken into estimation before migrating to ASP.NET: <\p>

Co-Existence The maiden and most important aspect that needs to be pat is the co-existence of ASP and ASP.NET. Both applications sack continue side therewith side on a server as the two systems have totally size processing engines. Also, separate file extensions (.asp versus.aspx) and separate angle models (metabase\registry dead against XML-based configuration files) are used between the two technologies. While relatively simple pages would in-migrate without any changes, more complex applications would require some modifications. <\p>

Migration Rationalization For migration, there are a number of approaches to command from. These include: Migrating an application for evaluation purposes Migration of the user interface tier of a system Migrating singular well-defined functionality, intending that i myself interoperates as a part as to the existing application Full fledge migration owing to devised reciprocal trade requirements Conduction Broken circuit The migration path needs to be carried based occurring the out-migration strategy that you opt pro. Vertical migration is the order used against go an application one run at a time. This strategy is most appropriate when minimal changes are conclusive to the interfaces between relentlessness tiers and the application EUR(TM)s modules are tightly coupled. Ego should opt to horizontal immigration if the application code needs against be migrated item by module, completing the migration for all three tiers in connection with ace module before moving in reference to to the next.<\p>