How to set the debugging of the ASP.NET application (including remote debugging)
Author: Han Feng Yu
Please choose according to your debug type and operating system, please do not reverse (if not, set it from the beginning)
PS: When you write this draft, use Win 2003, Win2000 Traditional Edition Visual Studio.Net 2003 English version, so the graphic map is not large, but the location of these "attributes" is constant.
First, local debugging
A. Windows 2000 operating system
1. Open the VS.NET tool option → Project web setting → Web server connection → ForntPage extension
2, users' group → delete "(192.168.0.1) Admins" user group "(may not be IP, is a computer name, no deletion)
3. Right-click "My Computer" → Administration → Services and Applications → Internet Information Management Server (IIS) → Right-click on "Default Web Site" All Tasks → Delete Server Extensions
4. Run "C: /Winnt/Microsoft.Net/framework/v1.0.0.0.05/ASPNET_REGIIS.EXE -I" under the MS-DOS command (may also be "c: /winnt/microsoft.net/framework/ v1 .1.4322 / aspnet_regiis.exe -i "), then find" UserName = "in" c: /winnt/microsoft.net/framework/v1.0.0.3705/config/machine.config "file "" Change to "UserName =" System "".
5, press step 3, "All Tasks" → "Configure Server Extensions" completion of the Wizard will be prompted to create a local user group "(192.168.0.1) admins" → refresh "User Group" to see, then Add this group of members
6. Right-click on "Internet Information Report" → Properties → Server Extensions → "Let the author upload executable";
7. Check the "C: / INETPUB / WWWWROOT" folder (note here is the root directory where the site is located, must be NTFS format) security attribute, there should be "(192.168.0.1) admins" user group, do not add itself And attach the corresponding power
8. Run the VS.NET, the new project will have the username and password prompt box, enter (192.168.0.1) Admins group members corresponding account and password (user password cannot be empty, if the account is not required, please add)
B. Windows 2003 operating system
1, the same
2, right-click "My Computer" → Administration → Service and Applications → Internet Information Management Server (IIS) → Site → Right-click "Default Web Site" → All Tasks → Delete Server Extensions 2002 → will open a web page, type " Administrator "and password, finished according to steps
3. Run "C: /Windows / Microsoft.net/framework/v1.1.1.4322/ASPNET_REGIIS.EXE -I" under the MS-DOS command
4. Right-click "Default Web Site" → All Tasks → Set Server Extensions 2002 → "Finish" → Click "Management" in the upper left corner → change anonymous access → Select "Open", "Participants"
5. Complete the above four steps, only the member of the Administrators user group has permission to debug, other users' debugging please refer to "Remote Debug" 2, remote debugging
First, first introduce the prerequisites for remote debugging:
1. Web server needs to be able to make local debugging conditions
2, the web server needs to install the Visual Studio .NET remote component, the client only needs "full remote debugging"
A. Windows 2000 operating system
1, you need to have a web server account, the account should be at least "debugger users" "WebAdmins" member (here I created a "cityhunter" account, "Web Admins" is setting up local debugging Created
2. Find " 3, the user must log in to the client computer with the username: "cityhunter" password: "123456" account .. This is the key for the server and the client in the same working group! ! The reason is perhaps the web server detects the account, only the account and password of the current client computer user, not the user entered when the user is entered. B. Windows 2003 operating system 1. Create a "cityhunter" account, password is "123456", add it to "Debugger Users" user group 2, right-click "My Computer" → Administration → Services and Applications → Internet Information Management Server (IIS) → Site → Right-click "Default Web Site" → New → Server Extensions 2002 Administrator → will open a web page, enter "Administrator" and password, finished by step, and finally this account should also be specially reminded within two working groups: This account also needs to be added to the IIS_WPG group (this is some part of 2005-01-18, if This initiates 'defaultapppool' startup errors, please understand) 3. Right-click "My Computer" → Administration → Service and Applications → Internet Information Management Server (IIS) → Application Pool → Right-click "DefaultAppPool" → Properties → Authentication → Specify as "CityHunter". Restart after completion. 4, the user must log in to the client computer with the username: "CityHunter" password: "123456" account. You can debug the project of the web server. After the above setting is complete, debug can be commissioned, and "W3WP.exe" (Win 2000 is ")" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" " It should be noted that the company's firewall cannot block the communication of the above programs.
