Update VS Code launch configuration to match .NET 5 migration #18992
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
Mailaender
changed the title
Mailaender
approved these changes
Jan 2, 2021
phrohdoh
changed the title
abcdefg30
requested changes
Jan 2, 2021
|
We're still not finished with migrating our development toolchain to .NET 5 and there are more breaking changes for launch.json to come. The macos and linux mono overrides will be removed, so should not be touched here. Instead, i suggest adding a windows-specific override for the program back to exe (or just wait, and fix everything together in the next PR). |
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.
5e74e58 has us producing and running
OpenRA.dllinstead ofOpenRA.exe, so update the VSCode launch config (without these changes, launching will fail with a file-not-found error).