Comments
Sort by recent activity
I went to use the tool on my old workstation and it uninstalled. Wow. This is rediculous! No longer will I recommend Reflector. :evil:
(BTW, I do have the paid for pro version on my primary machine, but this is SICK!) / comments
I went to use the tool on my old workstation and it uninstalled. Wow. This is rediculous! No longer will I recommend Reflector. :evil:
(BTW, I do have the paid for pro version on my primary machin...
This is super annoying and I've hit it more often than not. This combined with the opening/closing of the debug window has caused me to leave the addin turned off unless I'm using it.
With that said, I do have a suggestion that works for me. I think the toggling of ".NET Framework Source Stepping" is the trigger that confuses the internal PDB module laoding list. Before entering the debug session, go to the "Choose Assemlies to Debug..." menu option and let it load. You should see all the assemblies that you already selected are currently selected. Just hit OK (Continue?)!
It churns for a minute, hopefully without complaining about locked files.. and it shouldn't take very long. A few seconds later it finished. When I kicked off my app and set some breakpoints, I was no longer getting that annoying SET of dialog boxes. Maybe they should add a check when you go to debug an app that validates the PDB paths / lists, or whatever.
Hope this helps! I know it greatly reduced my stress level. I might even leave the addin enabled most of the time now. [image]
Cheers!
-Sean / comments
This is super annoying and I've hit it more often than not. This combined with the opening/closing of the debug window has caused me to leave the addin turned off unless I'm using it.
With that sai...
Thanks for the response! I don't have things running right now, but I was able to observe that if I wipe out all of the downloaded symbols and turn off ".NET Framework Source Stepping", then Reflector seemed to work as I would expect. It did have to re-download symbols (it seemed). If it works by generating PDB's with embedded source, then it does reason that as long as it uses those PDB's, then I would get what I need. I'm guessing the builtin PDB's (with a possible lack of code - as some framework assemblies seem to lack) may take precedence if they appear first in the symbol search path.
Again, thanks for the help. I'll be looking for this information in the documentation soon. If it's not there, I would highly recommend adding it! [image]
- Sean / comments
Thanks for the response! I don't have things running right now, but I was able to observe that if I wipe out all of the downloaded symbols and turn off ".NET Framework Source Stepping", then Reflec...
Good! It's kinda irrelevent to me what it's doing. All I know is that when I'm working from home, I need to disable the addin and restart visual studio when i'm debugging. (It's VERy annoying).
Can't you use the Visual Studio API's to issue commands without using the command window??
Thanks for the insight!
-Sean / comments
Good! It's kinda irrelevent to me what it's doing. All I know is that when I'm working from home, I need to disable the addin and restart visual studio when i'm debugging. (It's VERy annoying).
Can...