-
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
VS2022? #17
Comments
I don't have a Windows machine anymore, so I can't really work on this. Haven't used VS in years. But usually these only require a small change in the manifest file, so if someone feels like sending a pull request I could try to get this running. But I also saw in some other issue I think that this might be an option in MSBuild now, see https://docs.microsoft.com/en-us/dotnet/api/microsoft.build.tasks.msbuild.stoponfirstfailure?view=msbuild-16-netcore Although they say this is not meant to be used from user code it sounds like it does exactly what you'd want. |
Hi, in the next week, I can try leveraging this extension to VS2022. |
@shuelsmeier There's an artifact in the Actions tab, see https://github.com/einaregilsson/StopOnFirstBuildError/actions/runs/1421752718 You should be able to download a zip there with both the VS2019 and the VS2022 versions 🙂 |
The artifact has expired. Is there a chance this might get pushed to the Marketplace? |
builds-for-vs2019-and-vs2022 Expired |
builds-for-vs2019-and-vs2022 Expired |
Hello, I did take the project and republished it to marketplace for VS 2022: All credit is made to this repo, had no work with it other than to the publishing |
@tomasfil - Einar, the maintainer of this repository has passed away, leaving this project orphaned. I have assumed stewardship of his account on behalf of his widow. Would you like to assume ownership of this project? I would just archive this repo and add a message to the |
@gzur That's very sad. My condolences to his wife and yourself. |
Hi there,
I love this extension - it's super useful for complex F# solutions to save a ton of time with each compilation. Just wondering if you plan on tweaking this to support VS2022?
Thanks!
The text was updated successfully, but these errors were encountered: