-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/vs2022support #18
Feature/vs2022support #18
Conversation
Thanks! I'll try to get this out today. Does the marketplace now allow having different versions of the same extension for VS2022 and then for VS2019 and older? |
Ok, I see that the Marketplace does not yet support having two vsix files, but they plan on supporting it. When they do I'll publish a new version. Thanks a lot for the contribution! |
I just followed the official guide for upgrading visual studio extensions to 2022. Update a Visual Studio extension for Visual Studio 2022
|
Thank you for the great extension! Is there any chance you can make the download for VS 2022 available somewhere here on GitHub in the meantime? |
@daflotsch I've actually set up GitHub actions now to build the extension on every commit. You can click on Actions and click on the latest workflow run and find a zip file under Artifacts with both the VS2019 and VS2022 versions. Here is a link to the latest version today: https://github.com/einaregilsson/StopOnFirstBuildError/suites/4256964033/artifacts/110539000 |
What do you think about creating a second listing |
Adds support for Visual Studio 2022 to the extension. Tested with Visual Studio 2022 Preview 7.0.
Fix for issue #17