Address VS2017 and VS2019 compatibility issues #206
Merged
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 attempts to address compatibility issues that are likely contributing to some of the issues reported recently including installation issues and missing context menu options. This change does two things:
Updates prerequisite versioning requirements on Microsoft.VisualStudio.Component.CoreEditor based on guidance to address installation issues in some versions of VS2019. I believe this should fix This extension is not installable on any currently installed products. #179.
Based on a solution that worked for a similar issue, I migrated all projects from packages.config to PackageReference to address extension loading errors in VS2017. Fixes "StylerPackage did not load correctly" #175. This may address XamlStyler not showing in VS for Mac version 8.2 (8.2.0.1105) #199, which exhibits the same symptoms.