BUG: Visual InterDev 6.0 Debugger Doesn't Process Client-Side Breakpoints When Using Response.Redirect

ID: Q236094

The information in this article applies to:

Microsoft Visual InterDev, version 6.0

SYMPTOMS

The Visual InterDev debugger does not process client-side breakpoints when a Response.Redirect statement is used to redirect to the page in which the client-side breakpoint was set.

RESOLUTION

There are two workarounds for this problem:

After the page to which you were redirected loads, refresh the page. Your client-side breakpoint is processed.

Use a debugger statement if you have JavaScript in your client-side code:
```
<SCRIPT LANGUAGE=JavaScript>
   debugger;
   alert("client-side breakpoints will be hit here");
</SCRIPT> 
```
Or use a stop statement if you're using Visual Basic Scripting Editing (VBScript) in your client-side code:
```
<SCRIPT LANGUAGE=VBScript>
   stop
   MsgBox "client-side breakpoints will be hit here"
</SCRIPT> 
```
This forces the Visual InterDev debugger to break.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

Create two pages: Page_a.asp and Page_b.asp.

Add the following line of code to the second line of Page_a.asp:
```
<%Response.Redirect "page_b.asp"%> 
```

Save Page_a.asp.

Add the following code in between the <HEAD> tags of Page_b.asp:


<SCRIPT LANGUAGE=VBScript>
     MsgBox "client-side breakpoints will not be processed here"
</SCRIPT>

Set a breakpoint on the MsgBox line of code.

Save Page_b.asp.

Set Page_a.asp as the Start Page, and start the debugger using the Start button.

Notice the breakpoint is not processed.

Additional query words:

Keywords : kbASP kbDebug kbScript kbVisID600 kbVisID600bug kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug