This repository has been archived by the owner. It is now read-only.
VS2019 support #385
Open
VS2019 support #385
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
|
The priority of VS2019 compatibility should be increased, since the GA-Version has been around for quite a while (April 2nd). |
DjordjeMandic
approved these changes
Jul 18, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
fix based on https://madskristensen.net/blog/how-to-upgrade-extensions-to-support-visual-studio-2019/
Note: as there is a v5.6.199 available in the VSIX nightly build feed, you need to update the vsix version number, if you want to roll a custom build on your machine based on this PR.