How to configure your Web server for Visual InterDev 6.0 ASP debugging (192011)

MORE INFORMATION

Install/Confirm debugging components on the Web server

Install or ensure that you are running the following components:

• Microsoft Personal Web Server 4.0 or Internet Information Server 4.0 or later.
• Asp.dll version 4.02.0662 or later. If you have version 4.02.0662, the file size must be 330,448 bytes. You can install an updated version of Asp.dll by applying Windows NT Service Pack 4 or later.
  
  You may have to stop Web services before applying a service pack in order for Asp.dll to be updated. From a command prompt, you can type the following to stop the Web services:

  net stop iisadmin /y

• Microsoft FrontPage Server Extensions version 3.0.2.1706 or later.
• The Microsoft Visual InterDev Server components. If you do not see this listed in the Add/Remove Programs utility in Control Panel, you can install it by running Setup.exe from the VID_SS folder on Visual Studio CD-ROM 2 or on CD-ROM 1 of the Visual InterDev standalone version.
• Remote Machine Debugger components (recommended).
  
  If you do not see this listed in Add/Remove Programs, you can install it by running Setup.exe from the SCRPT_SS directory on Visual Studio disc 2 or on disc 1 of the Visual InterDev standalone version.
• Visual Studio Service Pack 3 or later, if you are running Windows 2000.

NOTE: The Web server must be a Windows NT 4.0 Workstation/Server or a Windows 2000 Professional/Server/Advanced Server computer.

Add the necessary users to the Local Administrators group of the Web server

In order to correctly use debugging, you must be part of the local Administrators group on the Web server you will be debugging against.

Steps to add users to the Administrators group in Windows NT 4.0:

1. From the Start menu, select Run.
2. Type usrmgr computer name and click OK.
3. Double-click the Administrators group in the bottom pane.
4. Add the users you want to allow to debug.

Steps to add users to the Administrators group in Windows 2000:

1. From the Start menu, select Programs, and then select Administrative Tools.
2. From the Administrative Tools menu, select Computer Management.
3. Expand Local Users and Groups under System Tools.
4. Select the Groups folder.
5. Double-click the Administrators group in the right pane.
6. Add the users you want to allow to debug.

Make sure that script file cache is on

Steps to verify that the script file cache is on in Low (in-process) applications:

1. Open Internet Services Manager.
2. Right-click the server name, and then click Properties.
3. On the Internet Information Services tab, click WWW Service under Master Properties, and then click Edit.
4. On the Home Directory tab, click Configuration.
5. On the Process Options tab, under Script File Cache, ensure that the Do not Cache ASP Files check box is not selected; you must enable one of the other options to cache ASP script files.

Steps to verify that the script file cache is on in Medium (Pooled) or High (Isolated) out-of-process applications:

1. Open the Internet Services Manager.
2. Right-click the application name, and then click Properties.
3. On the Directory tab, click Configuration.
4. On the Process Options tab, under Script File Cache, ensure that the Do not Cache ASP Files check box is not selected; you must enable one of the other options to cache ASP script files.

Configure DCOM permissions on the Web server

1. From the Start menu, select Run.
2. Type dcomcnfg.exe and click OK.
3. On the Applications tab, scroll down to the Catalog Class and double-click it to view Properties.
4. Select the Security tab.
5. Click Use custom access permissions and then click Edit.
6. Add the users that you will allow to debug (or simply add the Administrators group), and add the System and Interactive accounts, granting them Allow Access rights.
7. Select the Use custom launch permissions option and click Edit.
8. Add the users that you will allow to debug to this list, granting them Allow Launch rights, or simply add the Administrators group to this list.
9. Select the Identity tab.
10. Select the interactive user option.
11. Click Apply and then click ok.
12. Display the Properties for the Machine Debug Manager, and repeat steps 4-11 for the Machine Debug Manager.
13. In the Distributed COM Configuration Properties dialog box, on the Default Properties tab, make sure that the Enable Distributed COM on this server check box is selected.
14. Set Default Authentication Level to Connect.
15. Set Default Impersonation Level to Identify.
16. Close the Distributed COM Configuration Properties dialog box, and reboot your computer.

NOTE: The following are the minimum recommended accounts that should be in your DCOM permissions for both the Catalog Class and the Machine Debug Manager: Administrators, System, and Interactive.

Set up a Visual InterDev 6.0 project for debugging

1. Create a new Web project in Visual InterDev 6.0.
2. Add an ASP page to the project.
3. Add the following lines of code to the new ASP page within the HTML body:

   <%
   Response.Write "hello world"
   %>
   					

4. Right-click on the Response.Write line and select Insert Breakpoint. This will set a breakpoint for that line, and a large red dot will appear to the left of the line in the border.
5. Right-click on the file in the Project Explorer and select Set as Start Page.
6. From the Debug menu, select Start.
7. A dialog box should appear asking if you would like to enable ASP debugging on this project. Select yes.
8. You will then be prompted for debugging credentials. Use one of the accounts that you added to the Administrators group.
9. The debugger should break on your breakpoint, and the line should be highlighted. Press F5 to continue.NOTE: If remote debugging, the client is required to have Personal Web Server 4.0 or Internet Information Server 4.0 or later installed. ASP debugging is not supported on a Windows 95 or Windows 98 client.