Article ID: 236094
Article Last Modified on 10/16/2002
APPLIES TO
- Microsoft Visual InterDev 6.0 Standard Edition
This article was previously published under Q236094
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 are 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 that this is a bug in the Microsoft products that are 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.
Note that the breakpoint is not processed.
REFERENCES
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
244272 INFO: Visual InterDev 6.0 Debugging Resources
Keywords: kbbug kbscript kbdebug kbpending KB236094
