Visual Studio. NET error Collection (1)

First:
If you are using WINXP or win2kpro, you will not encounter this problem, because you can only put the website under the c: \ intpub \ wwwroot Directory, which defaults to http: // localhost, which is the local site directory and can be debugged without any configuration. If you are using the win2kserver version and want to solve this problem as soon as possible, you can use the IIS manager to change your solution directory to a virtual directory of localhost and debug it immediately, however, you must log on as an administrator.

Second:
Use System W: win2kserver to use a website directly defined by IIS. The procedure is as follows:
1. You must convert the logical partition of the local directory of your website to the NTFS partition. Otherwise, you cannot use the Asp.net debugging function.
In DOS mode, type A command
Convert [Partition Number, such as D:]/Fs: NTFS
Then the system says that the conversion must be performed after the next startup and then restarted. The hard disk partition of your website will become NTFS.
2. Open the IIS manager and select your website. In the shortcut menu displayed, select "delete Server Extension" under "all tasks"
3. After deletion, open the shortcut menu of the site and select "configure Server Extension" under "all tasks", except for defining administrator emails. After the server extension is installed, several users will be added to your user management.
4. Open Control Panel --> management tools --> Computer Management
Select User Management and add your logon username (if you are on your computer, log on to the system using administrator) to the following groups:
Debugger users
Vs developers
[Your Website IP address] admins
[Your Website IP address] authors

In addition, you can add the ASPNET users to the following groups (only on Development computers ):
Debugger users
Vs developers
[Your Website IP address] admins
[Your Website IP address] authors
Administrators
5. Close the user management window and the control panel. Open the IIS manager and open the Properties window of your website.
Add the following on the "operator" Page:
Administrator
Computer Name/ASPnet
Computer Name/Vs developers
Computer Name/debugger users
[This website IP address] adminis
[This website IP address] authors

Access and security in the directory --> anonymous access and authentication control --> edit --> integrated windows Verification

5. Close the site Properties window and select all tasks from the shortcut menu of the site --> permission wizard
Select Configuration from template, select public web site, and disable IIS manager after configuration.

6. Open vs. net, open the Project Properties window, go to "Configure properties --> debug --> debugger, and select Asp.net for debugging.
Select "frentpage" under "general attributes" --> "Web Settings"
Exit vs.net.

7. View IIS properties, search for ASP. NET options, and select the ASP. NET version to use.

Are you running a Windows version that allows Visual Studio debugger to automatically attach to a web application? If not, start the application without debugging and manually attach it.
Does your web application have a web. config file?
Does the Web. config file enable the debugging mode by setting the debug attribute to true? For more information, see debug mode in ASP. NET applications.
Does web. config contain any syntax errors? You can run a web application without debugging to check for syntax errors. (Select "start execution (not debugging)" from the "debug" menu )".) If a syntax error exists in Web. config, the detailed information is displayed.
Are you a member of the debugger Users Group? If you log on as an administrator, is the administrator in this group?
Have you created a project by specifying a specific IP address (for example, 100.0000300.400? NTLM authentication is required for Web Server debugging. By default, the IP address is assumed to be part of the Internet, and NTLM authentication is not performed on the Internet. To correct this problem:
When creating a project, specify the name of the computer on the Intranet.
-Or-
Add the IP address (http: // 100.0000300.400) to the list of trusted sites on your computer. (Select "Internet Options" from the "Tools" menu of Internet Explorer, and then select the "Security" tab ).
Does the computer running the IIS server have the Visual Studio. NET remote component installed?
Is IIS installed on a local computer (that is, a computer running Visual Studio. NET) after Visual Studio. NET is installed? IIS should be installed before Visual Studio. NET is installed. If it is installed later, you may need to repair the. NET Framework.

Is the URL of the project start page specified correctly? Is the extension and project directory correct?
Is IIS Security Settings correctly set? To verify this, check the "Default web site" settings.
Check IIS security settings for "Default web site"
1. select programs and administrative tools from the Start menu, and then click Internet Service Manager (Windows 2000) or Internet Information Service (Windows XP ).
2. In the "Internet Service Manager" or "Internet Information Service" dialog box, click tree control on your computer ). In the "web site" folder, find "Default web site ".
3. Right-click "Default web site" and select "properties ".
4. In the "Default web site properties" window, select the "Directory Security" tab and click "edit ".
5. In the "authentication method" dialog box, select "Anonymous Access" and "Integrated Windows Authentication" (if not selected ).
6. Click OK to close the Internet Service Manager or Internet Information Service dialog box.
7. Click OK ".
For the ATL server application, verify that the debug predicate is associated with your ISAPI extension.
For ASP. NET applications, make sure that the virtual folder of the application has the "Application name" set in "Internet Service Manager" or "Internet information service ".
Specify virtual folders for Web Applications
1. select programs and administrative tools from the Start menu, and then click Internet Service Manager (Windows 2000) or Internet Information Service (Windows XP ).
2. In the "Internet Service Manager" or "Internet Information Service" dialog box, click tree control on your computer ). Find the web application in the Web site folder.
3. Right-click "Default web site" and select "properties ".
4. In the "Default web site properties" window, select the "directory" tab.
5. Under "application settings", click "CREATE ".
The Application name appears in this box.
6. Click "OK" to close the "properties" dialog box.
7. Click OK to close the Internet Service Manager or Internet Information Service dialog box.
Web applications on remote servers
If the web application is on a remote server, check the following:
Have you run the correct installer to install ASP. NET/ATL server and remote debugger components on the server?
Are you a member of the debugger Users Group on the server? Do you have the access privileges necessary to debug processes running under the system account?
Depending on the security settings, ASP. NET applications may run in inetinfo.exe (IIS Process) or ASP auxiliary process aspnet_wp.exe. The aspnet_wp.exe process runs as a system. To debug an application running under aspnet_wp.exe, you must have the administrator privilege or edit the machine. config file for aspnet_wp.exe so that aspnet_wp.exe can run under your account. To debug an application running in inetinfo.exe, you must be an administrator on the computer running inetinfo.exe.
Depending on the security settings, the ATL server application may run under inetinfo.exe or the ATL auxiliary process dllhost.exe. To debug an application running in inetinfo.exe, you must be an administrator on the computer running inetinfo.exe, or use the Common Language Runtime Library application to configure DLLHOST to run as a specific user.
Are you using "Terminal Server" to try to debug Web applications on a remote computer? In Windows XP, remote debugging of Local Web applications can be performed using terminal servers. Not supported in Windows 2000 or Windows NT.
Web applications stored in visual sourcesafe and extended by Frontpage servers
If a web application is stored in visual sourcesafe and uses the FrontPage Server Extension as its web access mode, check the following:
Is visual sourcesafe on the same computer as the FrontPage Server or web server? If yes, you can use integrated authentication for debugging. (To check the "Integrated authentication" Settings, refer to this process to check the IIS security settings for the "Default web site .)
Another way to solve this problem is to change the Web access mode from FrontPage to file share ).
Change the Web access mode to File Share)
1. In Solution Explorer, right-click the project name and select "properties" from the shortcut menu ".
2. In the <project> properties page dialog box, open the "common properties" folder and select "Web Settings ".
3. Under "Web server connection", click "Web Access Mode" and select "file sharing" from the list box ".
4. Click OK to close the <project> properties page dialog box.
Manually attach
If you follow these troubleshooting steps and still receive an error message when you start debugging, you may need to manually attach it to debug the application.
Manually attach
1. Start the application without debugging. (Select "start execution (not debugging)" from the "debug" menu )".)
2. attach to the appropriate IIS process or auxiliary process. By default, the ATL server application is inetinfo.exe, And the ASP. NET application is aspnet_wp.exe. Use the following process to determine the process in which the ASP. Net or ATL server application runs.
Check under which process the ASP. NET application runs
1. Use Visual Studio. NET or another text editor to open the machine. config file of the application.
2. Find the following process model attributes:
Enable
If enable is set to true, the application runs under aspnet_wp.exe (this is also the default setting .)
If enable is set to false, the application runs under inetinfo.exe.
Check the process in which the ATL server application runs
1. In Solution Explorer, right-click the project name and select "properties" from the shortcut menu ".
2. In the <project> properties page dialog box, open the "Web deployment" folder and select "General ".
3. view the "Application protection" settings.
If this parameter is set to "low (IIS Process)", the application runs under inetinfo.exe.
If this is set to "medium (pool)", the application runs under the dllhost.exe process (same as other ATL server applications in the pool ).
If this parameter is set to "high (independent)", the application runs under the dllhost.exe process (different from other ATL server applications ).
4. Click OK to close the <project> properties page dialog box.

1: Check that "ASP. NET debugging enabled" is "true" in "configuration properties"

2: Confirm "DEBUG = true" in your "Web. config"

3: If you have installed wind2000 SP4, Run "regsvr32 I aspnet_isap.dll" on the command line"

4: view the site information in IIS, select "Directory Security", which includes "Anonymous Access and authentication control", and then click "Edit .. ", confirm that the" Integrated Windows Authentication "option is selected

5: Choose "ie"> "Security Settings"> "Custom Level" and check "automatically log on with the current user name and password"

6: Run c: \ winnt \ Microsoft. NET \ framework \ v1.0.3705 \ aspnet_regiis.exe-I

7: Control Panel-management tools-Computer Management-local users and groups-users, double-click the ASPNET user to add the Administrators

Http://support.microsoft.com/kb/415643/microsoft official documents on this question