如何通过预构建事件将24个项目从8.1 SDK重定向至Win10 SDK？

Absolutely, you can make this happen—you just need to pair the pre-build event with a script that automates updating the target SDK version in all your project files before MSBuild runs. Here's a step-by-step breakdown to get it done:

1. Lock down your target Windows 10 SDK version #

First, confirm the exact version number of the Win10 SDK you want to switch to (e.g., 10.0.19041.0 or 10.0.22621.0). You can find all installed versions in C:\Program Files (x86)\Windows Kits\10\bin.

2. Create a script to batch-update project files #

Use a PowerShell script (more flexible than batch files) to scan every .csproj/.vbproj file in your solution and replace the old 8.1 SDK target with your chosen Win10 version. Here’s a ready-to-use sample:

# Set your desired Win10 SDK version here
$targetSdkVersion = "10.0.22621.0"
# Grab all project files under the solution directory
$projectFiles = Get-ChildItem -Path "$PSScriptRoot" -Filter *.csproj -Recurse

foreach ($file in $projectFiles) {
    # Read the full content of the project file
    $content = Get-Content $file.FullName -Raw
    # Replace the 8.1 SDK target with your Win10 version
    $updatedContent = $content -replace '<TargetPlatformVersion>8.1</TargetPlatformVersion>', "<TargetPlatformVersion>$targetSdkVersion</TargetPlatformVersion>"
    
    # Optional: If you're targeting a Win10-specific .NET framework (e.g., net6.0-windows), uncomment this line
    # $updatedContent = $updatedContent -replace '<TargetFramework>net48</TargetFramework>', "<TargetFramework>net6.0-windows10.0.22621.0</TargetFramework>"
    
    # Write the changes back to the project file
    Set-Content $file.FullName -Value $updatedContent -Encoding UTF8
    Write-Host "Updated SDK version for $($file.Name)"
}

Save this as UpdateSdkVersions.ps1 in your solution’s root folder.

3. Hook the script into your pre-build event #

In the parent solution (the one that triggers this build via pre-build event), modify the pre-build command to run the script before calling msbuild.exe for your target solution. The command will look like this:

powershell -ExecutionPolicy Bypass -File "$(SolutionDir)UpdateSdkVersions.ps1"
msbuild.exe "$(SolutionDir)YourTargetSolution.sln" /p:Configuration=Release

Key things to keep in mind: #

• Execution Policy: The Bypass flag ensures PowerShell lets the script run without restrictions—adjust this if your environment has strict security policies.
• Portable Paths: Use MSBuild variables like $(SolutionDir) instead of hardcoding paths, so your setup works across different machines.
• Backup Safety: If you want to avoid accidental data loss, add a line in the PowerShell script to create backups of project files before modifying them (e.g., Copy-Item $file.FullName "$($file.FullName).backup").
• Project Type Flexibility: If your solution mixes project types (e.g., UWP + WPF), add a check in the script to only modify files that actually have the <TargetPlatformVersion> element.

Will this work reliably? #

As long as the script targets the correct XML element for your project type, this setup will run consistently. The pre-build event fires before MSBuild starts processing the solution, so all 24 projects will be using the Win10 SDK by the time the build kicks off.

内容的提问来源于stack exchange，提问作者Karlovsky120