-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Support vs2022 in VsTestV2 #17460
Support vs2022 in VsTestV2 #17460
Conversation
@ShreyasRmsft @v-pkoneti @ankit-arora12 @nadesu pinging everyone because I am not sure who is the owner of this area |
@abhadauria1 @Eswarnath Prudhivi, can you please look into this? |
@galakt , Can you please add more details around testing that was performed along with results from your dev testing? |
@rasunkar That is actually another my question: how do you test this tasks? |
You also have hack for version 16 azure-pipelines-tasks/Tasks/VsTestV2/versionfinder.ts Lines 14 to 18 in 8d4e33c
Is this hack still required? Should same hack be done for version 17? |
Will this change fix the following error I see when I updated my tests to .NET 7?
|
@RandyDanielson No, you updated tests to .net7, but net7 is not present at the moment of test execution |
Changes will be ported to #17858 |
Resolved in #17858 |
Task name: VsTestV2
Description: Support vs2022
Documentation changes required: Y
Added unit tests: N
Attached related issue: Y Fixes #16489 #15522
Checklist: