Updated .vsixmanifest to work on VS 2019 #86
Closed
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
|
If you deleted Also be aware that there is #85 (duplicate work) and that the VSIX will need to load asynchronously to work in VS2019 |
|
It works without the asynchronous patch in VS2019 but it is going to be obsolete later. But as it is a duplicate I'm closing mine. |
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.
-Added VS2019 version to .vsixmanifest
-Deleted Microsoft.VisualStudio.Shell.11.0 because it doesn't satisfy VS2019
Tested with VS2019 and VS2017, seems to work
Resolves #84