Hi,
I have a third party dll, which is part of my setup. In the past this dll was provided by the vendor with a higher version number, then they suddenly changed the version number of this file to a lower version (this already happens years ago). As result I need to set "Always overwrite existing file" for this file, otherwise the file is missing, e.g. after a major update or has the wrong version.
Now we started patching. The option "always overwrite" still needs to be set on the base setup, in case a customer is updating from an older version. Typically (especially when working with virtual machines) we are using ISO files, which are mounted into the DVD drive of the testing machine. That means, the product is installed (let's say version 10) to update the installed version 9. The Product Code of this version (V10) was changed to favor a major upgrade. The installation media is removed after installation.
Then the patch (V10.1) is going to be installed. Here we can investigate two different behaviors:
1) If the patch is just installed via double clicking on the msp file, the patch installation will fail because the source media is unavailable. The user has to provide the installation source (network folder) or DVD. In case of DVD it fails anyway on an UAC enabled system.
2) If the patch is installed unattended via our own updater, then its working fine. The updater is installing the patch with the option /qb to do not allow any user interaction, just status messages.
According to the log files, the reason why it fails in case 1) is, that the installer tries to reinstall the third-party-dll (due to "Always Overwrite"), but the file is not contained in the patch file (this is clear, it wasn't changed compared to original V10 setup). The installation in case 2) runs through, because it somehow worked completely different (its running more on MSI server side, as far as I understand).
As a workaround, I added the same file again to the patch into a new component and set the condition of the original component of the third party dll to "FALSE" to force an uninstall of this component. But the trouble is now starting again, hence we are preparing the next update. I run now into the same issues as before with update 1 without the workaround (file is not replaced or media is requested). Setting a component to "Always Overwrite" seems to break proper patching afterwards.
I built the installer of this version with Advanced Installer 9.9. To no break patching, I need to stay with this version (probably forever) as long as we will support this version. The first version and the first update are already released and can't be changed anymore.
The questions are:
1) Is this behavior a well known issue?
2) How do I add files with a lower version properly, so that patches are not broken afterwards?
3) What should I do in the future, with the next "Major Update" of our product to avoid similar problems?
Regards,
R.Mueller
FOLLOW US
Get the latest news in Application Packaging