Added support for VS 2019 and 2022 #32
Open
Conversation
This file contains hidden or 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
…tRecent Adding checkOnlyMostRecent
Add docs
|
Any chance to get compiled .vsix here please? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Hello, I have create a shared project with your source code, then renamed your existing dll project and installer project to append 2017, then created 2 new installers for 2019 and 2022 and a new combined dll project for 2019-2022. The references differe in all these implementation projects. I am not able to update the unit tests as I don't have an Enterprise licence to do the Fakes, but we should be able to do something similar. I'll leave it up to you if you want to merge this or not.