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

This article mainly explains "what you need to pay attention to when using the VS2003 version". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what do you need to pay attention to when using the VS2003 version?"

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 the VS2003 version, if the default code binding method is used, the server-side controls 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, then it is in aspx.cs.

A "protected TextBox MyTextBox;" is declared, and in VS2005, this statement 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"

Namespace ScalableHosting.Profile-> System.Web.Profile;ScalableHosting.Security-> System.Web.Security; while adding 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.

1. Under the Users menu are commands about user operations. In addition to the commands we used above to add user "Add User" and change password "Change Password", there are also delete user "Delete User" and edit user "Edit User" commands. The "Open SourceSafe Database" command is used to change the current SourceSafe database.

2. The Options dialog box under the Tools menu includes some project settings.

Here is a brief description of the main options for the VS2003 version:

(1) Allow multiple checkouts in the General page, if selected, allows multiple users to check out files at the same time. The default is not allowed.

(2) the Enable project security check box on the Project Security page indicates whether security is allowed for the project. This item is not allowed by default. "Rights by Project", "Right Assignments for User" and "Copy User Rights" under Tools are available only when this option is selected. Here we choose it.

(3) the Shadow Folders page is used to set the mapping of the project on the server. The project saves all version information of the file in SourceSafe in binary form. To create a directory on the server and map the project files to this directory, use this command. Select the SourceManager project in SourceSafe in "Set shadow folder for project" and select the directory to which the project is mapped in "Set shadow folder to", such as C:\ SourceManager_Shadow.

(4) the Web Projects page is used to set up the mapping of Web projects on the server. Select the MyWebApp project in SourceSafe in This project represents a Web Site, and fill in "http://localhost", the local Web server (you can also fill in other servers) in URL." Fill in the virtual directory to be mapped in Virtual Tools and the deployment directory in "Deployments path". This directory will become the mapping directory of the virtual directory specified in IIS.

3. "Rights by Project" under the Tools menu manages the permissions of projects in SourceSafe, as shown in the figure. There are four kinds of user rights, which correspond to R (Read), C (Check Out/Check In), A (Add/Rename/Delete) and D (Destroy) in Rights.

Select an item in the "roject" box on the left, and select the appropriate user on the right, and use the check box below to assign the appropriate permissions to the user. The "Rights Assignments for User" under the Tools menu is used to assign permissions to the selected user, and the result is the same as the command above.

Thank you for your reading, the above is the content of "what do you need to pay attention to when using the VS2003 version?" after the study of this article, I believe you have a deeper understanding of what you need to pay attention to when using the VS2003 version, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.