Export (0) Print
Expand All

ASP.NET Debugging: System Requirements

This topic applies to:

Visual Studio Edition

Visual Basic

C#

C++

J#

Visual Web Developer

Express

No

No

No

No

No

Standard

Yes

Yes

Yes

Yes

Yes

Pro/Team

Yes

Yes

Yes

Yes

Yes

This topic describes the software and security requirements for the following debugging scenarios:

  • Local debugging: Visual Studio and the web application run on the same machine. There are two varieties of this scenario:

    • The ASP.NET code resides on the file system.

    • The ASP.NET code resides in an IIS Web site.

  • Remote debugging: Visual Studio runs on a client machine and debugs a Web application running on a server machine.

Local debugging of ASP.NET applications requires Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP Professional, or Windows Server 2003.

Remote debugging of ASP.NET applications requires a local client Windows 2000 or Windows XP (any edition). The remote server must be running Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP Professional, or Windows Server 2003.

Windows 2000

You can use Visual Studio on a Windows 2000 client machine to debug ASP.NET applications running locally or on a remote server. The debugging client may be running Windows 2000 Workstation or Server, with or without Terminal Services. If the client machine is running Windows 2000 Workstation, you must install Microsoft Internet Information Services (IIS) before debugging.

Windows XP and Windows Server 2003

From a client machine running Windows XP Professional or Windows Server 2003, you can debug ASP.NET applications running locally or on a remote server. From a client machine running Windows XP Home Edition, you cannot debug ASP.NET applications.

For remote debugging, local and remote machines must be on a domain setup, or, if they are on a workgroup setup, both machines must be running Windows 2000 or Windows XP.

To debug the ASP.NET worker process you must have permission to debug that process. ASP.NET applications run as the ASPNET user by default. If the worker process is running as ASPNET, or as NETWORK SERVICE, you need Administrator privileges to debug it.

The name of the ASP.NET worker process varies by debugging scenario and by version of IIS. For more information, see How to: Find the Name of the ASP.NET Process.

You can change the user that the ASP.NET worker process runs under. On Windows 2000 and XP, you do this by editing the machine.config file on the IIS server machine. On Windows Server 2003, you do this by using the Internet Information Services (IIS) Manager. For more information, see How to: Run aspnet_wp.exe Under a User Account.

If you change the user to your own user account, you do not need to be an Administrator on the IIS server machine. If you change it to anything else, you have to be a member of the Administrators group in order to debug.

NoteNote

You should consider the consequences of the ASP.NET worker process getting hacked. The users ASPNET and NETWORK SERVICE have minimal permissions, which reduces the impact of successful hacking. If you must change the user to one with more permissions, then carefully consider the security implications.

Community Additions

ADD
Show:
© 2014 Microsoft