Dear Advanced Installer,
We tested your MINOR upgrades - when we are leaving the product code untouched - some years ago: back then it was not working, some files were simply not replaced, even if the new .exe came with newer versions of the affected files.
Now after upgrading to AI version 22.8, we performed some more tests, we hoped the issues with MINOR updates are fixed already. Unfortunately we got the same result: some files are still not replaced.
Test scenario:
1. We have a lot of files DLLs) with e.g. version number 1.0.0.0
2. We build an exe with version 1.0.0.0 and install it on a PC
3. We upgrade our DLLs and ALL of them have version 1.1.0.0
4. We build a 2nd exe with version 1.1.0.0 using the files in step 3
5. We install exe 1.1.0.0 over 1.0.0.0
Result: in our case 4 files were simply not replaced and they still had version 1.0.0.0. Most of the files have 1.1.0.0 version after the upgrade.
Note: those 4 files were probably used by Windows Explorer, as we got a "Windows Explorer needs to be closed" message during the installation, also the tray, and Windows Explorer was closed temporarily for 10-20 seconds. So we got the idea, that maybe a system reboot will fix those 4 files, but they still had 1.0.0.0 wrong version even after the reboot.
Are you aware of such problems of your MINOR upgrade mechanism?
Do you have any suggestions how we could create MINOR releases? We would like to start deploying smaller exe packages, with faster installation time, however those packages should be stable and should replace all of the files.
Best regards,
Zsolt