Hello!
I create patches for customers rollout. This is my patch structure:
- Version 7.3 (family)
-- Version 7.2 (target)
-- Version 7.1 (target)
the Version 7.3 is created with Advanced Installer 11.6, the other Versions are created with 11.4 or ealier. The patching from 7.1 to 7.2 was created without Problems. Now the patch from 7.1/2 to 7.3 is created without errors (only the warnings using different authoring tools, causes in the different versions of Advanced Installer). But the patch is not functionally. It patches only a view files. A view with Orca (opening 7.1 or 7.2 and view patch 7.3) offers, that the new version numbers are not applied. The patch uses the old version numbers. But some patched files has the correct version numbers.
I tried out to create a patch with InstallShield trial, based on the same MSI (7.1 or 7.2) and changed files. This patch has the correct version numbers.
Is this a known bug? When an update is released for this?
Twice, I saw that my main application file has the version with max(uint) (65535.65535.65535.65535). I think this behavior is, because the checkbox "Always replace" in the file properties was checked. I think that a warning should appear. This file is actually not capable patch, because it cannot have a higher version number in file table.
But just this file is patched. But the filetime is not correct on the target system. Can you explain this?
Greetings from Germany
Sylvio Spielhagen
FOLLOW US
Get the latest news in Application Packaging