By Ghulam Nabi Shah | April 28th, 2015 |
The very first thing to understand is that, making an ASP migration will boost an application’s performance. ASP.NET is an awesome platform for web development. If I had to choose between creating a new application in ASP.NET and creating a new application in ASP classic, ASP.NET would win, hands down. For starters, it’s faster and incredibly stable plus, once you’ve gotten the hang of ASP.NET it takes much less time to build an application.
Do you still think you really need an ASP migration?
ASP.NET is drastically different from ASP classic, yet, if you have a current application with ASP classic pages, they won’t run under ASP.NET without changes. If you want your existing applications to take benefit from ASP.NET, you need to make the ASP migration.
So what is the need for ASP migration?
Before truly making an ASP migration, the question should be asked, why would you want or need to migrate. If you don’t know by now, pages of Classic ASP and ASP.NET can be put in the same directory and can run in parallel. They differ in the extension, classic ASP comes with asp extension while ASP.NET with aspx extension. Although if the files exist in the same directory application wise it is different. The application object or session of the Classic ASP application cannot be utilized by the ASP.NET application and vice versa.
Information that needs to be available in both applications essentially need to be in a shared data store or must be replicated someway. For a scalable Classic ASP application, the session object associated needs to be replaced by an alternative solution. In a web or cluster farm, application data needs to be replicated to a shared data source. Large applications using COM objects can still be maintained in ASP.NET environment. There is no need to migrate such components, however it helps in improving performance.
Migration of .NET environment should be considered as an important task as sometimes ASP migration effort requires more time so that re-engineering the whole page or application may be a better idea. Although re-implementing the application is time consuming, it helps in leveraging the full advantage the ASP.NET offers.
There are several major phases in the ASP migration process. Let’s take a look at a few.
When you are ready for the ASP migration, the entire application should be copied to the location as required for working. Do you still think you really need to make the ASP migration? Watch my video blog on how I can help you find the best solution possible.