ASP-> ASP.NET migrate GUIDELINE qi 2003-08-26
Article Type: News
Difficult Level: 3/9 Version: 1.02
I have written a MIEC model theory on Weblog in July, and it is:
l migration
l interperation
l Eai
l .NET Connection
MIGRATION is most often used in the same application layer but on a different platform, such as a Web from from FROM, which is the ASP. NET, or the COM of the intermediate layer into web services, and so on. Basically, MIGRATION adjusts a layer that does not greatly affects other layers or the logic that has been running throughout the system.
You will find that MIEC mode theory is very useful. When your application needs to migrate from ASP2.0 to 3.0, you can process it as follows.
First stage - code conversion
Use a tool to convert the ASP code to the code of ASP.NET. Generally you can choose one of the following tools (these are also mentioned in my WebLog)
l asp2aspx --http://www.netcoole.com/asp2aspx.htm
l VB6-> VB.NET, Winform-> WebForm --www.artinsoft.com
l askBRIDGE INCLUDECONTROL --- http://www.iprisma.com/aspbridge/index.htm
Of course, I will use ASP2ASPX to complete the first phase of work, convert the ASP code to ASP.NET
Below is a 3.1 evaluation version, which can only convert an ASP code of no more than 1,000 lines.
Second stage - verification, finishing and testing
This stage is mainly to organize and stick to the first phase of the code to see if it has been transformed correctly. Generally, the specific code and application migration tasks are completed at this stage, and ensure that migration is functioning properly.
1. Since most of the ASP has no type, many are converted into system.object, you can do a little code reconstruction in the process of checking, modify system.object into some known types. , Such as System.String; System.Int32; System.Int64
Each of this part takes a complete unit test for each of the modules, or the adjustment of the code, mainly guarantees that the compilation can pass this batch file, or using the MS ACT, this tool is accessible to an ASP. Net is very good, especially multiple URLs, ACT will give you a successful or failed list.
2. Some ASP code needs to be modified, such as the SESSION code of the ASP, because these are no longer available in ASP.NET, this part of the code can only be overridden.
3. Migrate the part of the ADO code, tools can help you do some, but you need to check the transformation code, pay attention to the difference between ADO and ADO.NET, the most obvious thing is that you know that ADO.NET does not support the cursor of the server, specific Participate in the following resources.
4. Migrate the part of the COM component, the version after the ASP2ASPX 3.0 can automatically convert COM / ActiveX into a proxy's assembly, but you need to check and make some adjustments, first need to migrate first, then consider this method Performance, I suggest you put it in the next stage.
5. Here is a very large number of code workload, because the code generated by ASP2ASPX is very limited for "Code Behind", and the resulting code is almost all code and UI in an ASPX interface. ASP.NET 2.0 will have better support for this approach, but this will now have a certain amount of code. Third stage - optimization, integration, and deployment
This stage is mainly for the above situation, and integrating some optimized or more applications, and finally deploy after the test is completed.
1. Some of the code that calls the ADO section may need to optimize this phase to make full use of ADO.NET performance.
2. If there is a form of the original VBScrip COM component, you need to adjust the components in this stage, which is directly called .NET Assembily or it may be that in the ASP is called COM Proxy, then this situation is more important to pay attention. General you can do three options:
a) Change to the part of the database and business logic directly in the CS file of the ASP.NET page.
b) Establish a .NET Assembly overwrites or encapsulates the contents of the original COM components.
c) Change some components to Web Services.
3. Consider transform some of the UI into Server Control, put it in cache, or fully "code behind"
4. Consider using some COOL properties, such as check controls, regular expressions, sort functions, configuration class libraries, encryption functions, debugging, and tracking functions, multithreading, etc., enhance the performance and reliability of the original application.
5. Take two modes of EAI and .NET Connection, continue to enhance your web application's value, most obvious and common way, you will find that you will make this application into a company's Portal during the process of migrating the ASP application. Website (EAI mode), can also make your app to connect with a larger portal (.NET Connection mode) - Of course, I think this is the biggest benefit of migration, but it is often possible to go next one. The stage can really carry
6. Web services / remoting
Resource
ASP and ASP.NET Session sharing
SESSION principle
http://www.asp.net/forums/showpost.aspx?tabindex=1&postid=7504 (instructions for ASP.NET TEAM)
2. MSDN documentation
http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/converttoaspnet.asp
3. Third-party products and solutions
Http://www.consonica.com/solutions/dotnet/statestitch/index.html
http://www.sessionbridge.com/
MIGRATING to ASP.NET: KEY CONSIDERATIONS.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/aspnetmigrissues.asp
Migrating asp Pages To ASP.NET PAGES
Http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconmigratingasppagestoasp.asp
Converting asp to ask.nethttp: //msdn.microsoft.com/library/default.asp? URL = / library / en-us / dndotnet / html / convertasptoaspnet.asp
Upgrading to ADO.NET
Http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotNet/html/UPGRADINGTOTNET.ASP
ADO.NET for the ADO Programmer
Http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotNet/html/adonetprogmsdn.asp
Migrate Classic Asp to ASP.NET
http://www.aspalliance.com/anjum/aspmigration.aspx
An Experience In MigRating from Asp to ASP.NET
Http://www.mindfiresolutions.com/download/porting=asp to dotNet.pdf
Preparing your ask pages to migrate to asp.net
http://www.4guysfromrolla.com/webtech/041601-1.shtml
Microsoft .NET / COM MIGRATION ANDPERABILITY (PAG)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/cominterop.asp
MIGRATING YOUR ASP Apps from Windows NT 4.0 To Windows 2000
Http://msdn.microsoft.com/msdnmag/issues/0800/migrateasp/default.aspx
Web Service Facade for Legacy Applications (PAG)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/wsfacadelegacyapp.asp
MigRrating an asp-based site to an asp.net-based site (Microsoft Content Management Server 2002)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncomsrv02/html/mscs_csnetmig.asp
HOW to Upgrade ASP Pages To ASP.NET Pages That Use Jscript .NET
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnclinic/html/scripting01222002.asp
MigRating from ColdFusion To ASP.NET
Http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/coldfusiontoaspnet.asp
especially:
This article is originally owned by our WebLog. If you have any questions or suggestions, please email new2001@msn.com
