Compartilhar via

Visual Studio Breakpoint Helper

  • Artigo

I have created a prototype Breakpoint Helper that deals with the most common issues that Visual Studio Debugger users have when their breakpoints don't work. This is only a prototype, but I hope people will still find it useful.

If the feedback is promising I can try to get it integrated into VS2005.

If you have any comments on the helper itself, please use the Feedback section on this post. If you found it useful, I'd like to know. If it didn't help you, I also want to know, and please include the page name where it stopped being useful.

Please note I don't really want this post to become a 'here is my breakpoint problem please solve it' type of thing, as I cannot handle the volume and don't personally have all the expertise (especially ASP.NET issues). I really want people to try the helper and let me know where it has holes, is confusing, or unhelpful.

Comments

  • Anonymous
    June 04, 2004
    Hello,

    I just wanted to say that I absolutely love your tool, it's pretty handy in cases when you need to understand why a breakpoint isn't hit, just in case when you run out of clues.

    I have tested it and it's bold and clear, I think it would be great to try to integrate it into VS Team System analysis/help tools.

    Sorin Dolha [MCAD, MCSD .NET]

  • Anonymous
    June 06, 2004
    .:: Findekano's Tidbet ::

  • Anonymous
    June 08, 2004
    O(+>

  • Anonymous
    July 08, 2004
    The comment has been removed

  • Anonymous
    July 15, 2006
    Thanks.

    My breakpoint problem had me stumped for a couple of hours, finally after dozens of reboots I started web searching and ran into your site.  I was back debugging with breakpoints in a couple of minutes.

    -Tim

  • Anonymous
    August 06, 2006
    First, thank for the great site.
    native, vc8
    The dreaded yellow ball!
    First turn on "Warn if no symbols on launch".
    At least then you will get a dialog telling you.
    You can try and rebuild but sometimes
    vc8 incorrectly belives that symbols are out of date - the only fix is exit vc8 and restart.

  • Anonymous
    August 06, 2006
    So much for that fix, the hollow ywllow ball is back, and now vs doesn't even complain, just the hollow yellow ball the the ! icon on it.
    Any ideas?

  • Anonymous
    August 06, 2006
    The comment has been removed

  • Anonymous
    March 31, 2007
    I could fix the following problem I encountered when programming C/C++ in Visual Studio 2005: "The break point will not currently be hit. No symbols have been loaded for this document."I did the following: I went to the properties of my project, configuration, c/c++, general, format of debug information (I use a German version of Visual Studio so these categories might not be properly translated) and set it from "deactivated" to something else. Now the breakpoints work fine!

  • Anonymous
    April 19, 2007
    I have a problem that your helper does not help with.My icon has a question mark in it, and the tooltip says"No symbols have been loaded for this document."I had already tried.1) Ensure in Debug mode2) Rebuild3) Delete obj folder4) Close and reload projectFinally it worked when i1) Rebooted2) Rebuilt

  • Anonymous
    November 14, 2007
    The comment has been removed

  • Anonymous
    November 15, 2007
    jyoti: please use the Helper, as described at the top of this post.

  • Anonymous
    March 16, 2008
    hi, nice tool, but it did not help me with Visual Web Developer 2008. breakpoints work in a new project, but not an existing one. i checked the solution and project properties, seem to be correct on paths, but may be different than full Visual Studio thx

  • Anonymous
    March 17, 2008
    johny: Sorry, haven't tried VS2008 myself. Try Jim's blog (http://blogs.msdn.com/jimgries/) he has my old job on VS.

  • Anonymous
    September 14, 2008
    I use VS 2005 and had been trying to debug a device application. Breakpoins were working when running in device emulator, but not in the real device. Solution: There has been newer version of .NET 2.0 CF (SP1) in the device then in VS. So updating the .NET CF 2.0 to SP1 on the PC also solves the issue.

  • Anonymous
    September 22, 2008
    This is great, only I couln't find help for my problem. Once arrived at "The breakpoint will not currently be hit" the site does not offer the possiblility: "The specified module has not been loaded." This is my problem, and I can't seem to get the breakpoints working anymore. I'm using a combination of managed and unmanaged code. (But even in a simple new project (via wizard) the breakpoints don't work. Any help?

  • Anonymous
    May 19, 2009
    I couldn't find "Source File Paths" to check which file was being used as recommended. Where is it?

  • Anonymous
    May 20, 2009
    Margaret: Open Properties on the Solution.

  • Anonymous
    June 11, 2009
    Hey All, I too have wasted an inordinate amount of time on this one. Fortunately, our organisation has access to Microsoft Partner Support, who gave me this fix. It's a Compact Framework patch (I'm using CF2.0). As soon as I installed it, my breakpoints started working again!

  • Anonymous
    December 10, 2009
    The comment has been removed