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

How to solve the problem that VS2003 can not debug, I believe that many inexperienced people are at a loss about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Yesterday to today to do a whole day of computer, I almost crashed VS2003 can not be debugged!, can no longer be casually shut down, because this time carelessly, almost all the Net installation, debugging problems have been encountered by me, fortunately, I can not debug the record of the VS2003, after N times of search, finally came to a conclusion, is the problem of 2003 after 2005.

The following source networks:

Problem: when debugging the ASP program, an error was reported and the process "[3508] aspnet_wp.exe" automatically attached to the computer "LIUGZH" failed. The error code is 0x8013134b.

Answer:

Because when ASP.NET runs, the HTTP request made goes through IIS, and then IIS interviews aspnet_wp.exe for processing. So if the aspnet_wp.exe fails, the request cannot be completed. This problem should not occur until ASP.NET2.0 is installed.

First, method one. Uninstall ASP.NET2.0. The problem may be caused by installing ASP.NET2.0 before installing VS.NET 2003 (ASP.NET 2003 [Microsoft .NET Framework SDK v1.1]). You can try installing VS.NET 2003 before installing ASP.NET 2.0.

Second, method two. The modification steps are as follows:

1) enter inetmgr.exe in the runtime to open the IIS manager

2) there is an ASP.NET option in the properties of IIS

3) choose to use ASP.NET1.1 version from the drop-down box

Refer to the following figure

VS2003 cannot debug scenario 1

one. Pause IIS

two. Under C:\ WINDOWS\ Microsoft.NET\ Framework\ v1.1.4322, run aspnet_regiis / I to reinstall asp.net or from the start menu of Windows, point to programs, Visual Studio .NET 2003, Visual Studio .NET tools, and then select the Visual Studio .NET command prompt. When the window opens, type aspnet_regiis I.

three. Restart IIS

Option two, if option one doesn't work,

1 if the Web server uses a fixed IP: make sure that your "Internet Information Service" uses the "default web site" and that the IP address in the * is "(all unassigned)", not the ip address you have specified.

2 you can change the name of the "default web site", but do not delete it. Once deleted, the name can be restored as long as the name is strictly "default web site" when you create a new one.

3 if IE uses a proxy, check Bypass Proxy Server for local adresses. If you already have a web site, uninstall it without reinstalling vs.n

Generally solve the problem of unable to debug

The next word is, "the server does not support debugging ASP.net or atl server applications." I use the WINDOWS XP PROF version, I build the project like this, file-> New-> Project-> visual c # Project-> asp.net web application, and then enter the name to build a site, but once you click debug-> start will appear this error! Because of this error, the server simply ignored the c # control program I compiled.

It's true that I didn't install IIS until after I installed VS.NET, but it was the same error after I uninstalled vs.net. What should I do? Do you want me to write the WINDOWS XP and reinstall it?

It took me a long time to solve this problem. The method is as follows.

* species:

If you are using a WinXP or Win2kPro version of the system, you will not have this problem, because you can only put the site in the C:\ intpub\ wwwroot directory, which defaults to http://localhost, the local site directory, and can be debugged without any settings. If you are in the Win2kServer version and want to solve this problem as soon as possible, you can use IIS Manager to change your solution directory into a virtual directory of localhost, which can be debugged immediately, but you must log in as an administrator.

The second kind:

Using the system W:Win2kServer, using the website defined directly by IIS.

The steps to solve the problem that VS2003 cannot be debugged are as follows:

1. You must convert the logical partition where the local directory of your website is located into a NTFS partition, otherwise you cannot use the debugging feature of asp.net.

In Dos mode, type the command convert [partition number, such as D:] / fs:ntfs

Then the system says that it must be converted after the next boot, and then reboot, and the hard disk partition where your website is stored will become NTFS.

two。 Open IIS Manager, select your website, pop up a shortcut menu, and select "remove Server extension" under "all tasks".

3. After deleting, also open the shortcut menu of this site, select "configure Server extension" under "all tasks", except do not define administrator mail, everything else defaults. After installing the server extension, several users will be added to your user management.

4. Open Control Panel-> Administrative tools-- > computer Management

Select user Management, put your login user name (if you are your own computer, then generally log in using Administrator), and join the following groups

5. Close the user management window and close the control panel. Open the IIS Manager and open the properties window of your site.

On the operator page, add:

Administrator

Computer name / ASPNET

Computer name / VS Developers

Computer name / Debugger Users

[IP address of this website] Adminis

[IP address of this website] Authors

6. Open Vs.Net, open your project properties window, in "configure Properties-> Debug-- > Debugger, select asp.net debugging.

Select "FrentPage" under "General Properties"-- > "Web Settings"

Exit VS.net after confirmation

After reading the above, do you know how to solve the problem that VS2003 cannot debug? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.