Improve VSCode and VS C# instructions and mention "Build" button #4808
Conversation
This file contains 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
skyace65
changed the title
akien-mga
approved these changes
Apr 6, 2021
|
Thanks! |
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.
The separate debugging sections for VS Code and Visual Studio have been merged into the main setup instructions. I don't know why separate setup instructions were created in the first place, as there's no reason to keep this information separate. There were contradictions between the different sections regarding setup. As far as I'm aware what is in this PR is the correct way to set up both editors. I searched the docs and couldn't find any pages using the links to the debugging sections so I've removed them completely. closes #4802
Edit: I just changed one of the warnings to mention the build button in the upper right of the editor since I saw an issue about it. Figured I might as well do it now since I'm editing the page. I've also updated the 3.3 PR with that fix. Closes #4806