Running InstallAware setup over prior Wise version

[fletcherjames]

I am about to create a new setup kit using InstallAware, for an application we've had in the field for 7 years, which previously had a Wise installer (Installmaster-generated .exe, not WFWI).

I'm wondering whether:

a) we can just write the kit as if there were nothing special about the prior version (i.e. InstallAware will take care of uninstalling prior, automatically), or

b) we need to force people to manually uninstall the prior version before installing our new kit, or

c) We can tell people we're uninstalling, and they should re-start the new kit if there's a re-boot, and then just run the UnWise.exe package, or

d) We can get a way with just blowing away the prior UnWise.exe and the Install.log, and the Add/Remove programs entry (I suspect that would leave us with corrupted file usage counts.) or

e) You have another, better idea of how to handle the situation.

[lextm]

One quick note,

No matter what installation tech you use (WISE, Inno Setup, InstallShield, WiX), there should be enough information left in Registry under Local_Machine\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall if the application is already installed (I mean the old version).

So, in your new installer created with InstallAware, use MSIcode to analyze that information. In my project, I read the version number of installed old version application, locate the uninstaller there, run it to remove the old version. Then install the newer version.

It should be easy if you use a GUID to identify your application in WISE installer. Then in InstallAware, you should be able to continue using the GUID.

In sum,

a) (I do not try it but guess it works) use the old GUID or Application name in new installer may lead to this optimistic result.

b) Generally speaking, if you can uninstall old version using MSIcode, you should not let your users do it manually.

c) If there is a reboot when uninstalling old version, personally speaking I think a manual restart of new version installer is unavoidable.

d) "blowing away" is not unstandable.

[lextm]

About uninstalling old version,

If a reboot is required after uninstallation, you can add the "Reboot and Resume" command.

Refer to Help on this command.

[SteveDude]

If you are redistributing the entire app you could create an uninstall as a Pre-Req and then just launch unwise.exe. If you set suppress reboot message during silent installs/uninstalls in your original wise script install you can handle it in IA by a return code and run unwise with the /s commandline. May also need to pass it the log file name if you named it something other than install log.

I am doing this now with an installation that was done on old WiseScript 9.

You can also just create an update but there are some issues at times overwriting some files, so you may need to use delete recursive first to make sure they are replaced.