PowerShell install has different install location than setup.exe

[alex-frankel]

PowerShell installs to %USERPROFILE%\.bicep:
https://github.com/Azure/bicep/blob/main/docs/installing.md#powershell

Setup.exe installs to %USERPROFILE%\AppData\Local\Programs\Bicep CLI

[majastrz]

The PowerShell script was just a temporary solution until we had the setup.exe. I think the real fix here is to make setup.exe remove our files from %USERPROFILE%\AppData\Local\Programs\Bicep CLI and delete the directory if empty (we probably should not delete the directory if other files remain there in case the user put their own files in the directory).

[alex-frankel]

It would be nice if setup.exe would remove the reference to a powershell-installed version of bicep on the PATH, but not do that for any custom installs.