Hello,
I am currently using a software that has the capability to switch between different versions. For my specific use case, I need the software updater to automatically “update” to a lesser version (for example, from Version 1.1 to 1.0).
However, I have not found any configuration settings that would allow me to enable this functionality.
Edit: Using a .msi installer would be preferred due to compatibility reasons.
Is it possible to configure the updater to allow such downgrades? Any guidance or suggestions would be greatly appreciated.
Thank you!
Suggested Articles
Re: Configuring Updater for Software Version Downgrades
Hello and welcome to our forums,
Normally, Windows Installer does not allow the downgrade scenario.
However, at our user's request, we have implemented the option to allow a downgrade. You can set this in the "Upgrades" page of your Advanced Installer project.
However, I'm afraid this might not work with the updater.
Best regards,
Catalin
Normally, Windows Installer does not allow the downgrade scenario.
However, at our user's request, we have implemented the option to allow a downgrade. You can set this in the "Upgrades" page of your Advanced Installer project.
However, I'm afraid this might not work with the updater.
Best regards,
Catalin
Re: Configuring Updater for Software Version Downgrades
Hi,
thanks for your response!
I was able to find a solution using a custom EXE as detection method.
It seems to work almost fine, but I have one problem that I would need help with.
When the updater starts the installation of the "newer" version, my custom actions don't get executed for some reason.
I would need a custom action to execute a script, even when it's not a first-time-install.
How can I add a custom action in my installer that also runs on update?
Thanks for your help!
Best regards
Splinti
thanks for your response!
I was able to find a solution using a custom EXE as detection method.
It seems to work almost fine, but I have one problem that I would need help with.
When the updater starts the installation of the "newer" version, my custom actions don't get executed for some reason.
I would need a custom action to execute a script, even when it's not a first-time-install.
How can I add a custom action in my installer that also runs on update?
Thanks for your help!
Best regards
Splinti
Re: Configuring Updater for Software Version Downgrades
Hello Splinti,
Thank you for your followup on this and for sharing your solution with us!
Hope this helps!
Best regards,
Catalin
Thank you for your followup on this and for sharing your solution with us!
In the Custom Actions page --> your custom action, we should make sure that under "Execution Stage Conditions" --> "Show upgrade options", the "Upgrade" option is selected.How can I add a custom action in my installer that also runs on update?
Hope this helps!
Best regards,
Catalin
Re: Configuring Updater for Software Version Downgrades
Hello,
A quick update to this, just in case other users stumble accross this.
Being able to rollback to a previous version is not supported out of the box.
However, it is still possible.
To allow your customer to "update" to an older version, we firstly need the "Allow downgrade" option from the "Upgrades" page.
Besides that, we need a condition in our Update Configuration File that will allow the detection of the older version. For instance, we can use a condition that is always evaluated as false, e.g. a registry search for a version that looks for a version that does not exist, e.g. 10.0.0.
This way, if you install v3.0 and then check for updates, it will check and see the version being lower than 10.0.0 and will download v2.0 to install it.
Please be aware that this condition has to be changed, for instance, when we reach our 10th version.
Basically, we trick the updater into thinking v2.0 is an upgrade for v3.0 through the install condition.
Additionally, the "Do not try to detect if the update was installed" option should be checked in your Updates Configuration Project, under "Update Installed Detection" tab.
Hope this helps!
Best regards,
Catalin
A quick update to this, just in case other users stumble accross this.
Being able to rollback to a previous version is not supported out of the box.
However, it is still possible.
To allow your customer to "update" to an older version, we firstly need the "Allow downgrade" option from the "Upgrades" page.
Besides that, we need a condition in our Update Configuration File that will allow the detection of the older version. For instance, we can use a condition that is always evaluated as false, e.g. a registry search for a version that looks for a version that does not exist, e.g. 10.0.0.
This way, if you install v3.0 and then check for updates, it will check and see the version being lower than 10.0.0 and will download v2.0 to install it.
Please be aware that this condition has to be changed, for instance, when we reach our 10th version.
Basically, we trick the updater into thinking v2.0 is an upgrade for v3.0 through the install condition.
Additionally, the "Do not try to detect if the update was installed" option should be checked in your Updates Configuration Project, under "Update Installed Detection" tab.
Hope this helps!
Best regards,
Catalin