Crossing the debugging this 这 - Analysis of the problem that cannot be debugged
Friends using VS.NET may often encounter cases that cannot debug ASP.NET, and some friends give some viable solutions. Summary, generally includes the following aspects (please note: Discussions here are about local debugging solutions): - Determine if the current user has been added to the debugger user group - determine if the current user has Administrator permissions - Web Application The "Allow Debug ASP.NET" attribute in the project properties is set to True. You can also implement it by modifying the debug property of the Compilation element of the web.config file. It should be noted that the operating system required by local debug ASP.NET applications is Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP Professional, and Windows Server 2003. That is, we cannot debug your work on Windows XP Home, WindowsMe, and Windows 98. (Nonsense?) Under normal circumstances, it is basically possible to use the debugging of the ASP.NET in accordance with some of the above solutions. There is a problem, you should be able to reconfigure IIS by trying to use .NET_regiis.exe. However, this article hopes to discuss with everyone, how to debug the ASP.NET without this machine administrator permission. I heard it, is it not necessary? But if you think about it, you will recognize the need for this. The reason is very simple. In most management compared formal software companies, developers generally will not be granted to this machine Administrator privilege, so how to debug an ASP.NET application without this machine administrator permission, first need Solved questions. To this end, I will check some information (mainly MSDN Online) and summarize a viable solution and hope to share with you. Test Environment: Windows XP Professional SP1, Vistual Studio .NET 2002. First, add the current login user into the debugger user group (in addition, this user is at least the User Group. In most cases, the developer will be awarded POWER Users permissions). By the way, if you want this user to maintain a web virtual directory, you need to add this user to the VS Developers group. Of course, this is independent of whether it can debug an ASP.NET application. Next, according to Microsoft, if this user wants to debug the ASP.NET application under Windows XP Professional, you also need to add this user into the "Sign in" policy as a batch job (of course, other versions of debugging ASP.NET) Windows does not need to do this), so you can debug. This user can be added to the "Control Panel -> Administrative Tools -> Local Security Settings" Tools. Unfortunately, the result is not as mentioned in Microsoft's related documentation, it can be debugged after setting it. After a period of research, I found the answer from an article in MSDN Online. I believe that everyone knows that by default, the ASPNET_WP.EXE process is running in web server, and its username is ASPNET. In this case, how do we want to debug a web application, you must have this ADMINISTRATOR permission.
