Clean up stale binary after name change with windows msi updater

[pierremtb]

Recent beta builds are no longer renaming the binary in a bundle to productName, keeping the rust crate name.

The issue we're facing at KittyCAD/Zoo is that running the updater installs our new zoo-modeling-app.exe binary (new name) in the Zoo Modeling App directory, but doesn't remove the existing Zoo Modeling App.exe (old name), leaving it stale for the user to potentially get confused about.

Is there a hook we could use to run some type of clean up script for that stale executable as we forge ahead with the tauri dependency bump that requires this binary executable name change? I'm assuming other tauri users would be in the same boat as the rust crate names are much more restrictive on what characters they allow (for instance, no space).

Thank you!

[lucasfernog]

NSIS has installer hooks but I think this one should be handled by us @amrbashir

[olexiyb]

I feel it was a mistake to use package name instead of productName from tauri.conf.json
With old approach if you need to install multiple versions to test them separately on Windows it used to be

"Sanctum Dev"
"Sanctum Beta"
"Sanctum"
The commit brakes

• support of multiple version on windows
• support of human named link on windows

[jjh42]

I agree it's nice to have an easy way of setting beta/dev names so they can be installed alongside release versions.

[tweidinger]

Related for tracking:

• [feat] tauri migrate shoud migrate main bin name to product name #10548
• refactor(cli&bundler): avoid renaming main executable and preserve cargo name #9375
• Adds support for v1 compatible binary names in the bundler gitbutlerapp/tauri#1

[lucasfernog]

Closed by #10962 and #10967