Repository navigation
Fix PR-CI E2E jobs for the .NET 10 SDK / VS 2026 toolchain - #157
Merged
David Federman (dfederm) merged 1 commit intoJul 17, 2026
Merged
Conversation
The .NET 10 SDK (DotNetVersion '10.x') no longer supports VS2022, so the "E2E Tests using VS" job that installed VS2022 fails. - Remove the VS2022 E2E job. - Promote the former VS 2026 job (vs/18/stable) to be the canonical "E2E Tests using VS" job. - Install VS in the "tip of MSBuild repo" job: dotnet/msbuild's bootstrap build requires VS >= 18.6, which build.cmd locates via vswhere and the hosted image no longer provides.
David Federman (dfederm)
enabled auto-merge (squash)
July 17, 2026 21:08
John Erickson (johnterickson)
approved these changes
Jul 17, 2026
David Federman (dfederm)
deleted the
dfederm/fix-msbuildcache-e2e-vs-jobs
branch
August 6, 2026 22:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix PR-CI E2E jobs for the .NET 10 SDK / VS 2026 toolchain
Summary
The repo now builds against the .NET 10 SDK (
DotNetVersion: '10.x'), which is no longer compatible with VS2022's MSBuild. This breaks two of the PR-CI E2E jobs. This change updates.azuredevops/pipelines/pr-ci.ymlso the E2E jobs use a Visual Studio version that works with the current toolchain.Changes
aka.ms/vs/17/release/vs_buildtools.exe) is removed — its E2E test build fails because the .NET 10 SDK no longer works with VS2022's MSBuild.aka.ms/vs/18/stable/vs_buildtools.exe) becomes the single "E2E Tests using VS" job — the job id and display names drop the "2026" suffix while keeping the VS 2026 installer.vs/18/stableinstaller) is added before the "Build MSBuild" step. Buildingdotnet/msbuildat tip of main (build.cmd /p:CreateBootstrap=true) requires a full Visual Studio >= 18.6, located via vswhere. The hostedwindows-latestimage only ships VS2022 (17.x), so the build previously failed withNo instance of Visual Studio meeting the requirements specified was found ... -version 18.6. The installed VS is discoverable by vswhere regardless of install path and is also available to the E2E test that runs the bootstrapped MSBuild.Why
The move to the .NET 10 SDK / VS 2026 toolchain means VS2022 can no longer drive the E2E test builds, and building MSBuild at tip of main now demands VS >= 18.6 that the hosted image doesn't provide. The
vs/18/stablechannel currently provides VS 18.8, which satisfies MSBuild's >= 18.6 requirement.Testing / validation
These failures reproduce directly on the project's PR-CI: prior to this change the VS2022 E2E job and the MSBuild-repo E2E job fail, while the VS 2026 E2E job passes. This PR's own CI run provides the end-to-end confirmation that the updated jobs succeed.