Open paulgartner1 opened 2 years ago
Thanks for your effort. Did you check if the version you compiled for VS2022 still works for VS2019? In the past I noticed, that the NuGet-Roslyn packages where tied to specific VS versions. That's why there are multiple branches and multiple versions of this extension.
I've tested with both VS 2019 Pro, and VS 2022 Pro The single Vsix package is working with both.
Is this merge request good to pull in ? Finding the tool super helpful but constrained by the lack of 2022 support.
This should be good to go, I've built locally and been using in VS2022 for some time now without issue. @BADF00D , @davebally
@BADF00D are there any plans to release a new version of this extension for Visual Studio 2022?
Removed VS version suffix, can target multiple VS versions Update to version 4.0.0