Breakpoints stop working in VS2022
APrettyCoolProgram opened this issue · comments
I've been able to replicate this using the latest VS2022, and the .vsix of License Manager Header from here
When I set a breakpoint, and debug, the breakpoint (little red dot) disappears, and the code runs normally.
If I stop debugging, the breakpoint (red dot) is gone.
If I recreate the breakpoint, and debug, same thing happens.
In both cases, the breakpoint is listed in the Breakpoint Window prior to debugging, and disappears when I debug.
If I disable LHM, breakpoints work.
Re-enabling LHM causes breakpoints to stop working.
Right now I am leaving LHM disabled, but I sometimes re-enable to update my files. When I do that, I test breakpoints, and they don't work, so I disable LHM again.
This extension is freaking awesome, by the way. I've been using it for years, and it is a critical part of my workflow. I've migrated to VS22, and not having LHM suuuuuucks. I really appreciate your work on this, and if you need any additional information from me, let me know (I've never opened an issue on GitHub, so not sure what I should be providing).
@APrettyCoolProgram
Thanks for the report. Unfortunately, I can't reproduce this when working with the same binary on my VS2022. I'm assuming that it's something very specific that's not happening for 'standard' cases.
That's a bummer. At some point I'll dig into this further on my end.
Some additional information:
I've installed LHM on another machine. I'm pretty sure that this copy of VS2022 has the same extensions that my other machine has.
Breakpoints don't disappear when I debug BUT they do disappear when I right-click a file and "Add License Header". I can reproduce that behavior.
As for extensions, I pretty much only use those by Microsoft and Mads, so nothing crazy (that I am aware of).
EDIT: Another test - Using the LHM options, I've set it so LHM updates headers on "File.SaveAll". Now when I click the "Save All" button, breakpoints disappear from files that are saved.