Troubleshooting IIS 4.0 and Visual InterDev 6.0
by Ken Spencer
Published by 29th StreetPress
Dec.98; $24.95US; 1-58304-029-3
148 pages
Chapter 2 Using Active Server Pages (ASP) and HTML
|
 |
USING THE VISUAL INTERDEV 6.0 SCRIPT DEBUGGER
Before you can debug an application with the Visual InterDev 6.0
debugger, you must enable debugging for the application. Because enabling debugging places
extra overhead on the application, enable it only when you need to use the debug features.
Problem: You can't debug applications with the Visual InterDev
6.0 Script Debugger.
You haven't set the debugging options. You need to set them either in the Internet Service
Manager (ISM) MMC or in Visual InterDev 6.0. It is better to set the debug options for the
project you are working on in Visual InterDev 6.0 because that method enables debugging
only for that user's project while the user is executing it. Because it does not change
the settings for the application for all users, the application performs better for users
who are not debugging it.
Solution 1: Enable debugging using the MMC.
- Start the MMC.
- Select the Application you wish to change and display its Property pages.
- Click Configuration in the Application Settings section.
- Click the App Debugging tab (Figure 2.4).
- Check the options in the debugging flags section to enable either ASP server-side or ASP
client-side debugging.
- Apply the changes.
Solution 2: Enable debugging using Visual InterDev 6.0
The debug settings in Visual InterDev 6.0 are set on the Launch tab of the projects
Property pages. To set them,
- Start Visual InterDev 6.0.
- Open the project you want to change.
- Right-click the project name in Project Explorer and select Properties from the shortcut
menu.
- Click the Launch tab (Figure 2.5 on page 26)
- Check the options in the Server script section to enable ASP server-side debugging.
- Close the Properties pages to complete thechange.
Copyright © 1999 Ken Spencer
|
