BUG: The debugger does not hit a breakpoint in client-side script code in an ASP.NET Web application (320000)


The information in this article applies to:

  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
This article was previously published under Q320000

SYMPTOMS

When you debug an ASP.NET Web Application, the debugger does not hit a breakpoint that you set in the client side script code in a Web Form.

RESOLUTION

To work around this problem, follow these steps:
  1. Start to debug the program. The Running Documents window appears in Solution Explorer.
  2. In the Running Documents window, double-click the file name of the Web Form that appears in Internet Explorer to display the HTML source code in Code Editor.
  3. Set the breakpoint in the source code.

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

To reproduce the problem, follow these steps:
  1. Create a new default Visual Basic .NET ASP.NET Web Application project.
  2. Add a Web Form button to WebForm1.aspx.
  3. Switch to HTML view, and then add the following client script code:
    <script language="vbscript">
<!--
Sub Button1_OnMouseOver
form1.button1.disabled=true
End Sub
-->
</script>
  4. Set a breakpoint at the following line of code:
    form1.button1.disabled=true
  5. On the Tools menu in the Internet Explorer window, click Internet Options, and then click Advanced. Make sure that Disable script debugging is not selected.
  6. Press F5 to start the debugger. The Web Form appears in Internet Explorer.
  7. Move the mouse pointer over the button on the Web Form. The button is not available, but the debugger does not hit the breakpoint that you set previously.
Modification Type:MinorLast Reviewed:8/24/2005
Keywords:kbvs2002sp1sweep kbBug kbDebug kbpending KB320000
©2004 Microsoft Corporation. All rights reserved.