Shulou(Shulou.com)06/02 Report--

How to understand the experience of upgrading from ASP.NET1.1 to ASP.NET2.0? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and easy way.

It took a lot of time to upgrade CommunityServer to Asp.Net2.0 platform with a bag of cigarettes. Here's what I learned:

Vs2005 can easily help us upgrade the asp.net1.1 version project developed by vs2003 to the asp.net2.0 version developed by vs2005. Open the vs2003 solution or project file from vs2005, and there will be a wizard to help us complete the upgrade work. It is enough for some asp.net1.1 projects to finish this work.

However, most of the time, it will not be so smooth, but also pay attention to some problems:

The asp.net1.1 program developed by vs2003 will not check the syntax errors in aspx, aspcx and other files, while vs2005 will check the syntax in all aspx, aspcx and other files in the project, so if there are syntax errors, it will cause the compilation to fail.

In vs2003, if the default code binding method is used, the server-side control declared in the aspx file (take the aspx file as an example, the ascx file also has this problem) will generate a corresponding declaration in the aspx.cs file corresponding to the aspx file. For example, if a TextBox,ID is MyTextBox in aspx, a "protected TextBox MyTextBox" will be declared in the aspx.cs. In vs2005, this declaration is redundant, so remove these superfluous statements after the upgrade.

If a program uses Membership-- under asp.net1.1 and uses MemberRole.dll, to upgrade to Membership under asp.net2.0, you need to do the following:

Delete all references to "MemberRole.dll" in the project and add references to "System.Configration"

Change the namespace ScalableHosting.Profile-> System.Web.Profile;ScalableHosting.Security-> System.Web.Security; and add using System.Configuration

Remove all MemberRole.dll-related Membership configurations, refer to previous Membership configurations, add Membership configurations supported by asp.net2.0, and update Membership stored procedures.

This is the answer to the question about how to understand the upgrade from ASP.NET1.1 to ASP.NET2.0. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.