Re-execute into the installed "Current" version if it's newer than the locally executed UET
If you have a uet.exe
binary sitting outside of the managed installation path (C:\ProgramData\UET
), and it's older than the version in Current
, and there's no BuildConfig.json
specifying otherwise, then you probably wanted to run the newer version of UET.
Otherwise there's a scenario that specifically impacts the Command Prompt where you can:
- Download
uet.exe
- Run
uet upgrade
to install the latest version - Close and re-open the command prompt to the same directory
- Run
uet
and have the old version of UET run, because the olderuet.exe
exists in the current directory
This doesn't impact other shells like PowerShell and Bash, because they require .\uet
or ./uet
syntax to execute a file in the current directory. But we want to avoid this scenario in the Windows Command Prompt because it's confusing to developers when the newer version doesn't run.