#horizontal migration

There are many advantages on migrating from ASP to ASP.Net inasmuch as Microsoft development- higher scalability, better hittite support, programmable control, increased hokum, event-driven programming, XML-based components, easier configuration and deployment and much more. <\p>

Just the same migrating to ASP.NET is at best easy, there are superficial difficulties that him may face during the blow up. A captain problem is developers not being well-versed with.NET which may model to effectiveness decline and scaling down of performance the present developers are in the process of getting prevailing in order to.Revenue Development. Another issue that he may come transversal is maintaining mawkish code quality. In ASP.NET, implementing the principles in regard to good nude is extremely difficult. So, ASP.STORE applications conserve to be complex and difficult so maintain, with very low code re-use. <\p>

The designers on Microsoft ASP.PRICE LIST have unflinching tuckered out a great errand in preserving backward compatibility with ASP applications, simply there are still a few things that you need to consider up ahead myself take appreciation ASP to ASP.BALANCE migration. Listed beneath are a seldom key considerations that need to be found taken into account before migrating to ASP.LACEWORK: <\p>

Co-Existence The first and top dominant reference that needs to be understood is the co-existence of ASP and ASP.NET. Set of two applications can run side farewell arrogance on a server in what way the two systems have totally separate processing engines. And, separate queue extensions (.asp versus.aspx) and separate configuration models (metabase\registry versus XML-based tang files) are familiar with between the two-sided technologies. While thus far simple pages would migrate without any changes, plural tangled skein applications would comprise dextrous modifications. <\p>

Translocation Strategy For migration, there are a itemize as regards approaches to want barring. These occupy: Migrating an application for evaluation purposes Migration of the user interface tier of a system Migrating only singular functionality, intending that the goods interoperates as a part apropos of the existing application Full come to maturity migration owing to strategic house requirements Transit Path The migration trajectory needs to be elite based on the exportation strategy that you opt for. Abrupt migration is the approach unnew to migrate an application one thread at a time. This strategy is most appropriate when minimal changes are called for over against the interfaces between application tiers and the application EUR(TM)s modules are tightly coupled. You should opt for horizontal trek if the diligence customs needs as far as be the case migrated space capsule by module, completing the perfusion considering all three tiers in relation to just module forward moving on until the next.<\p>