How can we help you today? How can we help you today?

Strange problem. Cannot put breakpoint in my code

Hi all
I am not able to put breakpoints in one of my projects in a larger solution. I have searched the WEB for similar problems but nothing that helps. I have set the project to Debug, removed the "Optimize code" switch etc.

Then it hit me. What is different from the time I could put a breakpoint and now? I have installed RedGate Reflector 7. Allso, I have run the tool to let med dig into the framework with the debugger

Is there a bug in Reflector 7 perhaps that mix up something.

Please, I nead some help here
omheien
0

Comments

8 comments

  • Bart Read
    Hi there,


    Are you using Visual Studio 2010? I had exactly the same problem the other day, although it wasn't anything to do with Reflector because I didn't have the add-in installed at the time. I found that all breakpoints were being ignored, even though Visual Studio wasn't displaying any warnings about them - it didn't matter where I set them. Restarting Visual Studio seemed to fix the problem, although I've still no idea what caused it in the first place, other than VS seemed to be having a funny five minutes.


    HTH,


    Bart
    Bart Read
    0
  • omheien
    I was allso hoping this was not a Reflector situation, but I have restarted my computer many times now, same problem.

    I can copy the project to my lappy and the problem goes away. This lappy has Reflector 6.5.0.135 and no addin installed in VS2010 (Yes, its VS 2010)

    So then I'm back to my workstation with the problem. The only thing I can think of that is installed just before the problem started is the Reflector 7

    Any other help would be appreciated
    omheien
    0
  • Bart Read
    Thanks for getting back to me. I'm still baffled as to what's causing the problem, but one simple diagnostic is: can you set breakpoints again once you've uninstalled Reflector 7? I'd also double-check that there are no Reflector 6.x add-ins installed.

    On a slightly different tack, do you have any other VS add-ins installed? I wonder if there might be some odd interaction between Reflector and another add-in. There's nothing I'm aware of that should cause a problem, but it's possible there may be something like that happening.

    I'd also suggest, if you're not already using it, the 7.0.1.1 patch release, which you can get from from http://shop.reflector.net/download.

    One final question: which edition of VS 2010 are you using? Again, I'm not aware of any problems with specific editions, other than we don't support VS Express, but it might be helpful to know.


    Thanks,


    Bart
    Bart Read
    0
  • Bart Read
    I really am clutching at straws here...

    You don't say what kind of projects are in your solution, but this wouldn't be the problem, would it?

    http://forums.asp.net/t/1532854.aspx

    Also, are you seeing the "The Breakpoint will not currently be hit: No symbols have been loaded ... " warning message for breakpoints you do set?


    Thanks,


    Bart
    Bart Read
    0
  • Bart Read
    One final question: which OS version and bitness are you running?
    Bart Read
    0
  • omheien
    Just remembered what the last thing I did just before this happend:
    I red that I could let Reflector create some sort of layer over the framework letting me run the debugger through the .net framework. Can it be somethign in there ?
    omheien
    0
  • omheien
    I uninstalled Reflector and now the problem vannished. I have re installed Reflector and problem is still gone. I wil not try to regenerate the framework layer to be able to run the debugger through the framework. I suspoect that this was the problem.
    omheien
    0
  • Bart Read
    Hi there,


    Sorry for not responding earlier. Thanks for getting back to me. I'm glad the problem seems to have gone away.

    Obviously if you don't regenerate assemblies, it's not possible to debug into them. Perhaps it would be worth trying to regenerate just one of the framework assemblies you use in your solution, and then see if the problem comes back or not? I'd really appreciate knowing what happens.


    Many thanks,


    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.