UI for update

[Roman B.]

Hi.

I'm in the final stages of evaluating your product. There are still a few issues to resolve, but currently the update process is the most important one.

I'm trying to figure out the best way to create an installation package which will be used for both fresh install and update. What I want is to present the user with an appropriate UI which will indicate that the current installation process is actually an update installation process.

The two options I'm considering:
1. Using a minor upgrade (bootstrapper):
Each time a setup package is needed for a new application version, the Product Version is changed and Product Code untouched.
By default, the bootstrapper applies minor upgrade silently without showing any UI at all. If /qf option is added in the bootstrapper settings screen, the "Resume" UI sequence will be shown. But obviously this UI sequence is not suitable for update process.

I think I have read somewhere on these forums that minor upgrade should not be used to update services. However, when I tried to use the setup as described above, the installer has presented me with an option to shutdown the services and then restart them, which is fine for me. Are there any possible implications I'm not aware of?
Is there any way to use another UI sequence when minor upgrade is applied?

2. Using a major upgrade:
Each time a setup package is needed for a new application version, the Product Version and the Product Code are changed.
The "First Time Install" UI sequence has to be conditionally modified to adapt it both for first install and update.


It seems that from the perspective of MSI definitions for upgrades, minor upgrade is enough for what I'm trying to accomplish (only change the Product Version and update a few files) but I'm missing the UI to accompany it.

Do you think one of the presented options above can work well or maybe you could suggest a better one?

I would appreciate your assistance.

[mihai.petcu]

Hello,

Thank you for your interest in Advanced Installer and for taking the time to evaluate it.

I'm trying to figure out the best way to create an installation package which will be used for both fresh install and update.

If you're looking to accomplish this, then using a patch is not a solution. This type of upgrade can only be installed on computers that have the previous version already installed.
The differences are underlined in the Creating Patches article or here.

What I want is to present the user with an appropriate UI which will indicate that the current installation process is actually an update installation process.

Here's the How do I conditionally show the "UpgradeDlg" dialog? to help you with this.

Do you think one of the presented options above can work well or maybe you could suggest a better one?

Here's a similar "How to upgrade?" thread with related debated doubts to help you decide depending on your scenario.

(only change the Product Version and update a few files) but I'm missing the UI to accompany it

If this is the upgrade case, you can use a patch. Can you please specify the details you would expect from the UI in this case?

All the best,
Mihai

[Roman B.]

Hi Mihai.

If you're looking to accomplish this, then using a patch is not a solution. This type of upgrade can only be installed on computers that have the previous version already installed.

I meant creating a full installation (not a patch) project which will be able to do both (with bootsrapper's help, if I decide to do updates using minor upgrade).

(only change the Product Version and update a few files) but I'm missing the UI to accompany it

If this is the upgrade case, you can use a patch. Can you please specify the details you would expect from the UI in this case?

I would like the UI to indicate the currently installed version and the version to which the package is going to be updated. Also, similarly to what happens when a minor upgrade is applied with a full UI switch, present the user with an option to shutdown services which are needed to be updated and then restart them.

[mihai.petcu]

Hello,

I meant creating a full installation (not a patch) project which will be able to do both (with bootsrapper's help, if I decide to do updates using minor upgrade).

There's no need to distribute both a patch and a major upgrade in an installation package if this is what you mean. A full installation can be installed on any machine whereas the patch can be installed only on machines which have a previous version already installed. Distributing a package that contains both is not exactly best installer practice.

Maybe the Advanced Updater can help you organize your upgrade scenario. It will also automatically show only the newer available versions so the user is in full control and knowledge of the upgrade.

Also, similarly to what happens when a minor upgrade is applied with a full UI switch, present the user with an option to shutdown services which are needed to be updated and then restart them.

Unfortunately patching a service is not supported by Windows Installer. Here's the "Patching a Windows Service" thread that debates this.

All the best,
Mihai