Add support for VS2022 #113
Open
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
|
I think this might be redundant with https://marketplace.visualstudio.com/items?itemName=MadsKristensen.AddNewFile64 (Also, I don't believe your version 22.0 is correct — VS 2022 is, a bit confusingly, 17.0.) |
|
Ah, I wasn't aware of the new version of the extension. I couldn't find it when I searched. Either way, with the current version number whilst it may be incorrect, it does work - so I'm not particularly sure what the deal with that is. :) |
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.
This pull request simply modifies the VSIX manifest to allow installation within Visual Studio 2022. The extension works perfectly well in my testing whilst using Visual Studio 2022, and I've encountered no issues. Therefore, I thought I'd simply make a simple pull request to add support to the VSIX.
Modifying the manifest will allow the version check to pass within 2022, making the extension compatible. All existing functionality works perfectly well.