Skip to content

chore: standardize ToolsVersion to "12.0" across all .vcxproj files#1372

Draft
Copilot wants to merge 1 commit intomainfrom
copilot/analyze-develop-branch
Draft

chore: standardize ToolsVersion to "12.0" across all .vcxproj files#1372
Copilot wants to merge 1 commit intomainfrom
copilot/analyze-develop-branch

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 22, 2026 •
edited
Loading

  • Fetched develop and created fresh branch fix/standardize-toolsversion from it
  • Analysed all .vcxproj files on develop — found 18 with non-standard ToolsVersion
    • 2 files: 4.0 → 12.0
    • 10 files: 14.0 → 12.0
    • 6 files: 15.0 → 12.0
  • Applied single-attribute fix to all 18 files (opening <Project> tag only)
  • Verified: exactly 18 files changed, no other modifications
  • Committed and pushed fix/standardize-toolsversion
  • Open PR targeting develop

@JakobL-MSFT
chore: standardize ToolsVersion to "12.0" across all .vcxproj files
cd41f9c 
18 project files had stale ToolsVersion values (4.0, 14.0, or 15.0).
MSBuild ignores this attribute at runtime and always uses the installed
version, so this is a safe, no-build-impact cleanup that aligns every
sample with the repo-wide convention of ToolsVersion="12.0".

Agent-Logs-Url: https://github.com/microsoft/Windows-driver-samples/sessions/78824510-e04e-4e65-8568-799249aebc46

Co-authored-by: JakobL-MSFT <110699333+JakobL-MSFT@users.noreply.github.com>
Copilot AI requested a review from JakobL-MSFT April 22, 2026 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JakobL-MSFT JakobL-MSFT Awaiting requested review from JakobL-MSFT

Assignees

@JakobL-MSFT JakobL-MSFT

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@JakobL-MSFT