HOWTO: Configure ASP Debugging for Visual InterDev 6.0

ID: Q192011

The information in this article applies to:

Microsoft Visual InterDev, version 6.0

SUMMARY

This Knowledge Base article will briefly describe the steps involved to set up Active Server Pages (ASP) Script debugging for use with Visual InterDev Version 6.0.

NOTE: It is required to have the server components installed on the server for debugging to work.

MORE INFORMATION

Configure Windows NT Permissions for Users Who Need to Debug

In order to correctly use debugging you must be part of the administrators group on the Internet Information Server (IIS) server machine.

NOTE: Microsoft understands that this is a limitation and any new information regarding this issue will be posted in the Knowledge Base.

Using the User Manager for Domains, add the Windows NT user account that will be used for debugging to the administrators group. Only one account can be used for debugging at a time. Granting permissions to a group such as the Administrators group is not recomended.

Configure DCOM Permissions

From the Start button, click Run on the server computer.

Type dcomcnfg.exe and click OK.

On the Applications tab, scroll down to the Catalog Class and select it (single click).

NOTE: The Catalog Class item is installed with Back Office Installation Wizard and is part of the Server components for Visual InterDev 6.0

Click the Properties button to display the Properties dialog box.

Click the Security tab.

Select Use custom access permissions and click Edit. Add a user who is part of the administrators group on that machine. Grant the user Allow Access rights.

Select Use custom launch permissions and click Edit. Add the same user here and grant them Allow Launch rights.

Select Use custom configuration permissions and click Edit. Add the same user here as well and grant them Full Control.

Select the Identity tab.

Select the This user option for the user account you want to run for this application.

Type in the domain and userid of the user who you added in the above steps.

Type that user's password both in the Password and Confirm Password boxes.

Click OK to exit the Catalog Class Properties dialog box.

Display the Properties dialog box for the Machine Debug Manager item.

Repeat steps 4-13 for the Machine Debug Manager.

Select the Default Properties tab on the Distributed COM Configuration Properties dialog box.

Ensure that the check box for Enable Distributed COM on this server is selected.

Set the Default Authentication Level to Connect.

Set the Default Impersonation Level to Identify.

How to Set Up a Visual InterDev 6.0 Project for Debugging

Create a new Web project in Visual InterDev 6.0.

Add an Active Server Pages (ASP) page to the project.

Add the following lines of code to the new ASP page within the HTML body:
```
<%
DIM temp
temp = "Hello World"
Response.Write(temp)
%> 
```

Click in the border area to the left of the second line (temp = "Hello World"), this will set a breakpoint for that line. A large dot will appear next to the line in the border.

Right-click the ASP file name in the Project Explorer and select the Set As Start Page option.

A dialog box appears asking if you would like to automatically set the application into debug state. Click Yes and continue.

A dialog box appears prompting you to log on. Log on using the account you granted access to previously for debugging. This invokes the Visual InterDev script debugger. The debugger breaks on your breakpoint, and the line is highlighted.

REFERENCES

For more information, please see the "Microsoft Visual InterDev 6.0 Debugging" white paper on the Microsoft Developer Network (MSDN) Online:

http://msdn.microsoft.com/vinterdev/technical/articles/debug.asp

Please see the following articles in the Microsoft Knowledge Base for more information regarding Visual InterDev Debugging:

Q199004 INFO: VI6 ASP Debugging Not Supported in Windows 95/98

Q230507 PRB: Can't Find Project on Web Server or Set Server Debugging

Q196378 HOWTO: Debugging Active Server Pages Applications Manually

Q216668 PRB: VI Debugger Doesn't Close Connections When Stopping

Additional query words:

Keywords : kbide kbVisID600 kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbhowto