寻求PowerShell自动化多版本递进升级脚本方案

Absolutely! You don’t need to manually code every single version combination—this is exactly the kind of repetitive task PowerShell was built to automate. Here’s a scalable, easy-to-maintain script that lets you specify a start and target version, then automatically runs all the required intermediate installers in order:

Key Assumptions First #

To make this work smoothly, we’ll rely on a consistent naming convention for your installer files (e.g., MyApp_v4.exe, MyApp_v5.msi, etc.). If your files follow a different pattern, you can tweak the script to match—more on that later.

The PowerShell Script #

# Require administrator privileges (most installers need this)
$currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
if (-not $currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Write-Error "⚠️ This script needs admin rights! Please restart PowerShell as Administrator."
    exit 1
}

param(
    [Parameter(Mandatory=$true, HelpMessage="The current version the client is running (e.g., 2)")]
    [int]$StartVersion,
    [Parameter(Mandatory=$true, HelpMessage="The target version to upgrade to (e.g., 8)")]
    [int]$TargetVersion
)

# Validate input to avoid logical errors
if ($StartVersion -ge $TargetVersion) {
    Write-Error "❌ Start version must be lower than target version. Double-check your inputs!"
    exit 1
}

# --------------------------
# Update these values to match your environment!
# --------------------------
$installerRootPath = "C:\YourSharedInstallersFolder" # Path where all your installers live
$installerFileNamePattern = "MyApp_v{0}.exe" # e.g., "MyApp_v3.exe" for version 3
$silentInstallArgs = "/quiet /norestart" # Adjust to match your installer's silent flags (e.g., MSI uses "/qn")

# Loop through each required version and run the installer
for ($currentUpgradeVersion = $StartVersion + 1; $currentUpgradeVersion -le $TargetVersion; $currentUpgradeVersion++) {
    $installerPath = Join-Path -Path $installerRootPath -ChildPath ($installerFileNamePattern -f $currentUpgradeVersion)

    # Check if the installer exists before trying to run it
    if (-not (Test-Path -Path $installerPath -PathType Leaf)) {
        Write-Warning "⚠️ Installer for version $currentUpgradeVersion not found at $installerPath. Skipping this version..."
        continue
    }

    Write-Host "🔧 Starting silent install for version $currentUpgradeVersion..." -ForegroundColor Cyan
    $installProcess = Start-Process -FilePath $installerPath -ArgumentList $silentInstallArgs -Wait -PassThru

    # Verify the install succeeded
    if ($installProcess.ExitCode -eq 0) {
        Write-Host "✅ Version $currentUpgradeVersion installed successfully`n" -ForegroundColor Green
    } else {
        Write-Error "❌ Installation failed for version $currentUpgradeVersion (Exit Code: $($installProcess.ExitCode))"
        # Uncomment the line below if you want to stop the script immediately on failure
        # exit $installProcess.ExitCode
    }
}

Write-Host "🎉 All required upgrades completed! Your app is now at version $TargetVersion." -ForegroundColor Green

How to Use This #

1. Customize the environment values: Update $installerRootPath, $installerFileNamePattern, and $silentInstallArgs to match your actual installer setup. For example, if your installers are MSI files, change the pattern to MyApp_v{0}.msi and use /qn for silent args.
2. Run the script: Open PowerShell as admin, then run:

   .\UpgradeScript.ps1 -StartVersion 2 -TargetVersion 8
   

Extra Tips for Robustness #

• Add logging: Use Start-Transcript at the top of the script to record all output to a log file, which is helpful for troubleshooting failed installs.
• Handle reboot requirements: If some installers require a reboot, adjust the silent args (e.g., /forcerestart) and add logic to check for pending reboots before continuing.
• Support non-numeric versions: If your versions use semantic numbering (e.g., 2.1, 3.0), you can modify the script to use [version] type instead of [int] for version comparisons.

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