Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use VS2022 for CI Build #1112

Closed
CharliePoole opened this issue Jan 25, 2022 · 1 comment · Fixed by #1114
Closed

Use VS2022 for CI Build #1112

CharliePoole opened this issue Jan 25, 2022 · 1 comment · Fixed by #1114
Assignees
@CharliePoole
Labels
Build
Milestone
3.15.0-beta1

Comments

@CharliePoole
Copy link
Collaborator

This is a pre-requisite for #1044
@CharliePoole CharliePoole added this to the 3.15.0 milestone Jan 25, 2022
@CharliePoole CharliePoole self-assigned this Jan 25, 2022
@CharliePoole CharliePoole mentioned this issue Jan 25, 2022
Merged
@CharliePoole CharliePoole modified the milestones: 3.15.0, 3.15.0-beta1 Feb 7, 2022
@CharliePoole
Copy link
Collaborator Author

This issue has been resolved in version 3.15.0-beta1

The release is available on:
GitHub.
NuGet packages are also available NuGet.org and
Chocolatey Packages may be found at Chocolatey.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CharliePoole CharliePoole

Labels
Build
Projects
None yet
Milestone
3.15.0-beta1
Development

Successfully merging a pull request may close this issue.

Use VS2022 in CI Windows Builds nunit/nunit-console
1 participant
@CharliePoole