vs2022/vs2026 support, added native code debugging, symbol load, and jit/ngen optimization toggles as well #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mitchcapper
changed the title
…ter updates Work to support VS2026, full symbol load just launches the options->symbols page.
mitchcapper
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closing #23 in favor of this
Fixes #22
This is much larger now but I integrated a few other key debugger controls I often find myself having to dig out of various settings /windows.
Doing this is not as simple as just an option toggle like before. Nearly each of these needed to touch something different. I tried to add new helpers to do most of the heavy lifting but also brought in the VSIX Community Toolbox to make some things less difficult.
0 Effort was put into older VS support. I am sure if it does break some things (if) fixing wouldn't be a big deal but as I don't know if this will be accepted and VS2022 is all I needed that is where I left it. Some projects do have a separate VS2022 version while maintaining the older ones separately.