An org-wide audit of the dotnet org found pervasive references to VS2019 and Windows Server 2019 VM images. Windows Server 2019 ended mainstream support in January 2024.

Part of .NET OS Support Tracking. See also: dotnet/runtime#125690, dotnet/dotnet-buildtools-prereqs-docker#1605.

Tracking

• azure-pipelines.yml — build.windows.10.amd64.vs2019 → current VS image
• eng/common/templates/job/execute-sdl.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates/job/publish-build-assets.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates/job/source-index-stage1.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates/job/onelocbuild.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates/post-build/post-build.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates-official/job/publish-build-assets.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates-official/post-build/post-build.yml — windows.vs2019.amd64 → windows.vs2022.amd64
• eng/common/templates-official/job/source-index-stage1.yml — windows.vs2019.amd64 → windows.vs2022.amd64

Note: Several of these are in eng/common/ which is typically synced from dotnet/arcade. The fix may need to come from updating the arcade SDK version.

Details

https://github.com/dotnet/spark/blob/fdc3deb2868b7a13137b13f8bcda38677d3afdcf/azure-pipelines.yml

This issue was generated by GitHub Copilot CLI v1.0.7 via the update-supported-os skill.