When performing an upgrade of an existing product, how do I tell AI to install the same features into the same places that the user selected before? ISE does this without a problem so I suspect AI does it as well.
Also, is there anyway during these upgrades to not have the license and other screens come up? The user should be presented with a screen asking if they want to upgrade to the new build, if they select yes it just does it, if they select no it exits.
Thanks for the help.
Suggested Articles
Hi,
There is no way to force a MSI to install in the exact location of the previous version. Windows Installer does not support it and neither does AI.
However there is no need for that as the user might want to change the install location when he/she upgrades. In this case the application will be uninstalled from the old location and installed in the new one.
Regarding the dialogs I'm afraid that you cannot condition a dialog not to appear during an upgrade. But the license agreement might be different for the new version and the user should see it.
Regards,
Mihai
There is no way to force a MSI to install in the exact location of the previous version. Windows Installer does not support it and neither does AI.
However there is no need for that as the user might want to change the install location when he/she upgrades. In this case the application will be uninstalled from the old location and installed in the new one.
Regarding the dialogs I'm afraid that you cannot condition a dialog not to appear during an upgrade. But the license agreement might be different for the new version and the user should see it.
Regards,
Mihai
Mike,
While I agree that sometimes the license agreement may change it is really a pain for an administrator who has my product installed on many systems in his department to remember how they configured each one. More often, they simply want to install the same configuration (path and options) as they did the last time. Again, ISE (and ISP) do this now with their Windows Installer based products. It is obvious to me that IS realizes this to be the case as well.
At some point does AI plan on creating similar functionality?
While I agree that sometimes the license agreement may change it is really a pain for an administrator who has my product installed on many systems in his department to remember how they configured each one. More often, they simply want to install the same configuration (path and options) as they did the last time. Again, ISE (and ISP) do this now with their Windows Installer based products. It is obvious to me that IS realizes this to be the case as well.
At some point does AI plan on creating similar functionality?
I am thinking something similar. Although AI says that this is not part of the Windows Installer I know that other installers do this very thing (all Installshield products for one). I will write some information to the registry then when the user goes to perform an upgrade, I will read the information, launch an unistall, then launch an install with the correct command line options so there is not a user interface presented.
I noticed that even the AI patch presents the user with the license agreement and install type. I am assuming that AI is typcially used for smaller installs (one user or installs with minimal features). My product is typically installed by an administrator on many systems he/she has ownership of. It is crazy for anyone to think that this person is going to remember the install path and options that they installed on each system. And since my product has several features it can be very compilicated.
I really like a lot of the features of this product but it seems to be missing some rather obvious ones (to me).
I noticed that even the AI patch presents the user with the license agreement and install type. I am assuming that AI is typcially used for smaller installs (one user or installs with minimal features). My product is typically installed by an administrator on many systems he/she has ownership of. It is crazy for anyone to think that this person is going to remember the install path and options that they installed on each system. And since my product has several features it can be very compilicated.
I really like a lot of the features of this product but it seems to be missing some rather obvious ones (to me).