aspire install ps1 shows error message but then reports it succeeded when it didn't

[DamianEdwards]

On Windows, I had the staging channel of the CLI already installed.

Then I ran irm https://aspire.dev/install.ps1 | iex to install latest stable and this is what I saw:

➜ irm https://aspire.dev/install.ps1 | iex
Downloading aspire-cli-win-x64.zip from 'ga/daily'
Move-Item:
Line |
 636 |              Move-Item -Path $TargetExePath -Destination $backupPath - …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The process cannot access the file because it is being used by another process.
Remove-Item: The process cannot access the file 'C:\Users\dedward\.aspire\bin\aspire.exe' because it is being used by another process.
Aspire CLI successfully installed to: C:\Users\dedward\.aspire\bin\aspire.exe

The aspire cli is now available for use in this and new sessions.

It seems it failed to perform the logical rename of the downloaded file because the existing aspire.exe was locked by another process. Oddly I couldn't find any instances of aspire.exe already running?

A few issues here:

• The exception is uncaught and bubbles up as a raw error to the end user
• The script continues and renders the success message
• The install didn't actually succeed as I still have the staging version (13.2 in this case) installed