Talk:Auto-uninstall old before installing new

Jeff's comments

In the second example, doesn't that assume that the old version's uninstaller is called 'uninst.exe' and that it resides in the same directory we're trying to install the new version into? The first example is using the value stored in the uninstall string key in the registry, which is a more robust way of doing it.

Also, in the first example, shouldn't you have a second parameter to iferrors?

 IfErrors uninstall_failed uninstall_succeeded
   uninstall_failed:
     ;You can either use Delete /REBOOTOK in the uninstaller or add some code
     ;here to remove the uninstaller. Use a registry key to check
     ;whether the user has chosen to uninstall. If you are using an uninstaller
     ;components page, make sure all sections are uninstalled.
   uninstall_succeeded:
     ;now you won't do the above deletion or whatever if the uninstall succeeded.

Hans's comments

Please correct me if I'm wrong but as far as I know NSIS is not able to perform a "safe/consistent uninstallation" at all.

Scenario:

 (1) the installer GUI pops up
 (2) the user changes some settings
 (3) but finally the user decides to abort the installation

Since the installation has been canceled by the user I would expect that the system is left untouched - the old installation is still present.

But if we call the uninstaller in the onInit callback then the old installation is gone.

What NSIS is needs is another callback, e.g. an onPrepareFinished callback or something like that.

maybe it's possible to perform such on uninstallation in the onGUIEnd callback?

but for silent installation the onGUIEnd callback is not called at all.

Possible solution:

 have one central function to perform the uninstallation (e.g. doMyUnInstall)  and then ...
   in the onGUIEnd callback call doMyUnInstall
   in the onInit callback check with the IsSilent function. If Yes call doMyUnInstall