I have a question regarding "Uninstall a package with the same version (if found)". I am using AI 14.0.2 and deploy an app that heavily relies on the customer environment, which we can't always fully replicate in our test systems. So I have to ship bugfixes to the customer for their approval before packaging them as "full" versions and counting up the version number. Sometimes I need three or more versions until visible bugs and all subsequent problems hiding behind them are fixed.
For ease of use, the bugfixes have to be shipped as an installer. I understand that Windows Installer usually only allows updates with an upgrade package, which requires an increase of the first three parts of the version number. To be able to quickly deploy to the customer's environment without artificially blowing up the version number, I have thus enabled "Uninstall a package with the same version (if found)" to be able to install packages of the same version over one another.
But to always know which version of the installer a customer has on his disk (official version or a testing/approval version), I now want to count up the last part of the installer's version number when sending out these bugfixes for approval; e.g. 2.0.0.0 -> 2.0.0.1. But the package is only uninstalled if the version is exactly the same, e.g. 2.0.0.0; the "Uninstall a packages with the same version" switch does not use the same logic as the Windows Installer upgrade process. So if I try to install the version 2.0.0.1 over the version 2.0.0.0, with the .1 denoting my test patch 1 prior to releasing a working version 2.0.1.0, this fails with the error message "a different version of the product is currently installed".
Can I change this behaviour somehow? What I want to achieve is that I can freely install any 2.0.0.x over 2.0.0.y versions, e.g. 2.0.0.1 over 2.0.0.0 and 2.0.0.0 over 2.0.0.1, without the detour through "Programs and Features".
FOLLOW US
Get the latest news in Application Packaging