BUG: Visual InterDev Debugger Skips Client-Side Breakpoints (319423)

SYMPTOMS

When the Insert breakpoints in Active Server Pages for breakpoints in client script option is turned on in Visual InterDev, the debugger does not stop at client-side breakpoints in pieces of code formatted in a specific way. As the debugger passes the breakpoint, you receive the following error message:

"Source code is not available for current statement"

The icon that indicates the location of the breakpoint changes to a yellow exclamation point.

RESOLUTION

Use the DEBUGGER statement to indicate client-side breakpoints. For example, to stop before you run the line that reads x=0;, use the following code:

    var x;
    debugger;
    x = 0;

MORE INFORMATION

Steps to Reproduce the Behavior

Start Visual Interdev 6.0.
On the Tools menu, click Options.
In the Feature Selection tree, click to select Debugger.
Click to select the check box next to Insert breakpoints in Active Server Pages for breakpoints in client script.
To add an Active Server Page to the project, right-click the project name in Project Explorer, and then click Add.
In the Add Item dialog box, click Open.
Insert the following code in the body of the page.

NOTE: In the following code sample, there are seven blank lines between the Script tag and the function declaration.
```
<script language="JavaScript">







function doSomething()
{
    var x;
    x = 0;
}
</script>
					
```
Set a client-side breakpoint on the line that reads x=0;.

You can do this if you click the gray vertical bar to the left of the line, or if you put your pointer at the start of the line and press F9.
Press F5 to start the debugger.

REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

244272 INFO: Visual InterDev 6.0 Debugging Resources

192011 HOWTO: Configure Your Web Server for Visual InterDev 6.0 ASP Debugging