Addresses issue #55 for 0.4.0 release to select debug host bitness. #82
+30
−0
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
…bitness. This change adds a new debugger configuration to the package.json file. The user can simply change the debug type from 'PowerShell' to 'PowerShell x86' in their launch.json file to do 32-bit debugging. Also, when they open a folder that doesn't have a .vscode\launch.json file, when they go to create that file, they can pick between 'PowerShell' and 'PowerShell x86'. Of course on 32-bit OSs the 'PowerShell x86' selection is redundant with 'PowerShell'. Oh well.
|
Awesome! I think this will make some folks happy. |
daviwil
added a commit
that referenced
this pull request
Feb 4, 2016
…4-debugger Addresses issue #55 for 0.4.0 release to select debug host bitness.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change adds a new debugger configuration to the package.json file. The user can simply change the debug type from 'PowerShell' to 'PowerShell x86' in their launch.json file to do 32-bit debugging. Also, when they open a folder that doesn't have a .vscode\launch.json file, when they go to create that file, they can pick between 'PowerShell' and 'PowerShell x86'. Of course on 32-bit OSs the 'PowerShell x86' selection is redundant with 'PowerShell'. Oh well.