Share via


How to: Enable Web Server Debugging on Windows Vista

This topic applies to:

Edition

Visual Basic

C#

C++

Web Developer

Express

Topic does not apply Topic does not apply Topic does not apply Topic applies

Standard

Topic applies Topic applies Topic does not apply Topic applies

Pro and Team

Topic applies Topic applies Topic applies Topic applies

Table legend:

Topic applies

Applies

Topic does not apply

Does not apply

Topic applies but command hidden by default

Command or commands hidden by default.

Windows Vista provides enhanced security. To enable Web server debugging on Windows Vista, you must perform the following additional steps on the Web server host computer. Administrator privileges are required.

Note

Windows Vista does not support FrontPage Server Extensions. Therefore, when you want to open a Web site in Visual Studio, you must open it from a file share or an FTP share. In the Open Web Site dialog box, you cannot use the Remote Site. You can use the File System option and type a UNC path, and then set the Web server path in the Project Properties page. Or, you can use the FTP Site option.

To enable Web server debugging on Windows Vista

  1. In Control Panel, click Classic View.

  2. Choose Security Center.

  3. In Windows Security Center, click Windows Firewall.

  4. In the Windows Firewall window, click Allow a Program through the Firewall.

    The User Account Control dialog box appears.

    1. If the UAC dialog box requests your permission to continue, click Continue.

    2. If the UAC dialog box requests your Administrator password, type your password and then click Submit.

    The Allow a Program through the Firewall dialog box appears.

    Steps 6-9 open the TCP 80 port, which must be opened for ASP.NET, ASP, and ATL Server debugging.

  5. In the Add a Port dialog box, follow these steps:

    • For Name, type a description such as Web Server Debugging.

    • For Port Number, type 80.

    • Select TCP.

  6. (Optional) Limiting access to the your local subnet limits the numbers of users who could exploit the security hole you are opening. You should do this unless you have to debug outside your local subnet.

    1. Click Change Scope.

    2. In the Change Scope window, select My network (subnet) only.

    3. Click OK to close the Change Scope dialog box.

  7. Click OK to close Add a Port dialog box.

  8. Click OK to close the Windows Firewall dialog box.

  9. Close the Windows Security Center.

See Also

Tasks

How to: Set Up Remote Debugging