Script debugging not hitting breakpoints in Visual Studio 2005

I had a curious case recently where a customer was unable to get script debugging to work in Visual Studio 2005. By not work, I mean we could set breakpoints but they were just never hit. It was like the debugger wasn't listening. In the end this was one of those problems where we just sort of stumbled upon the solution.  I did a remote session with the customer to look at their desktop, saw the problem happening and then started to look at the browser configuration.  When the browser or things related to it start misbehaving, it is always a good idea to disable as many add-ins, popup blockers, toolbars etc and see if the problem still occurs. If it does not, re-enable half of them and see if the problem comes back. If it does, disable half of that half and see if the problem goes away again. If it does etc etc. By process of elimination you find the problem add-in.

In this case the thing that was stopping script debugging from working was the SSVHelper browser helper object (BHO) which is part of the Sun Java Runtime package:


Strange thing is that although disabling it on the customer's system allowed script debugging to work again, on my system I have the same thing and script debugging works fine. We never got to the root cause on this one, just had to put it down as "one of those things".



Comments (3)

  1. imRahulSoni says:

    To quickly check if an add-on is your problem: Right-click on the Internet Explorer 7 icon and select "Start without Add-ons"

    If you don’t find IE 7 icon on your desktop, do the following…

    On Windows XP — From the Display Properties select the Desktop Tab — then Customize Desktop — you’ll find the Internet Explorer check-mark.

    On Windows Vista — From the Appearance and Personalization section select Personalization — in the top left corner click "Change Desktop Icons"



  2. Thanks for the tip Rahul, very useful!

  3. Fred Exley says:

    I had the same problem with the debugger not hitting the breakpoints, and stumbled upon this as the cause:

    I had recently added a script in the aspx page, which ran instead of the same event (Page_Load) in the C# code-behind.  Moving the script code to the Page_Load event in the code-behind, and then deleting this script from the aspx page fixed the problem:

    <script runat="server">

    private void Page_Load(object sender, System.EventArgs e)


    if (!Page.IsPostBack)


    //sow.DataSource = ";;

    sow.DataSource = ";;





Skip to main content