PowerShell脚本效率优化：替代大量if语句及改进Start-Sleep方案问询

Hey there, nice work getting your initial script up and running—let's break down solutions to your two core questions to make this more efficient and maintainable:

1. Avoiding Massive if Statements for Multiple Apps #

Instead of writing separate if blocks for each application, you can use a collection of apps (like an array or hashtable) and loop through them. This keeps your code DRY (Don't Repeat Yourself) while retaining the interactive "install or skip" prompt for each app.

Here's a practical example using an array of app names and their corresponding executables:

# Define your list of apps: each item is a hashtable with friendly name and executable path
$applications = @(
    @{ Name = "Chrome"; ExePath = "C:\Installers\chrome_installer.exe" },
    @{ Name = "VS Code"; ExePath = "C:\Installers\vscode_installer.exe" },
    @{ Name = "Slack"; ExePath = "C:\Installers\slack_installer.exe" }
)

# Loop through each app to prompt the user
foreach ($app in $applications) {
    # Add input validation to ensure valid user choices
    do {
        $userChoice = Read-Host -Prompt "Would you like to install $($app.Name)? (Yes/No/Y/N)"
    } while (-not ($userChoice -match '^(yes|no|y|n)$'))
    
    # Make the check case-insensitive so any valid input works
    if ($userChoice -match '^y(es)?$') {
        Write-Host "Starting installation of $($app.Name)..."
        # We'll fix the sleep issue next, but this launches the exe and waits for it to finish
        Start-Process -FilePath $app.ExePath -Wait
    } else {
        Write-Host "Installation of $($app.Name) was skipped"
    }
}

This approach scales easily—just add more entries to the $applications array instead of writing new if blocks. The do-while loop ensures users can't enter invalid text that breaks the script.

2. Replacing Start-Sleep with Process Wait Logic #

The fixed 30-second sleep is inefficient because it either cuts users off too early or wastes time waiting when the install finishes quickly. Instead, use the -Wait parameter with Start-Process—this tells PowerShell to pause execution until the installer process exits naturally.

Here's how to update your original single-app script:

$userChoice = Read-Host -Prompt 'Would you like to install MyApp? Please type Yes or No'

# Case-insensitive check for yes/y
if ($userChoice -match '^y(es)?$') { 
    Write-Host "Launching MyApp installer... (script will resume once installation completes)"
    Start-Process -FilePath "MyApp.exe" -Wait
} else { 
    Write-Host "Installation of MyApp was skipped" 
}

If your installer spawns a child process (and the initial exe exits immediately), you might need to track the main installation process explicitly with Wait-Process:

$installProcess = Start-Process -FilePath "MyApp.exe" -PassThru
$installProcess.WaitForExit()

This waits for the specific process you launched to finish, even if it spawns other background processes.

Bonus Optimization: Clear User Feedback #

Adding simple status messages (like "Starting installation of X...") helps users understand what the script is doing at each step, making the workflow feel more intuitive and less "black box".

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