Hi,
While building a patch family I get the error "PackageCode {GUID} is not unique"
The patch setup is:
Upgraded 1 = MyApp.exe v4.11, Target is MyApp.exe v4.10
Upgraded 2 = MyApp.exe v4.12, Target is MyApp.exe v4.11
The {GUID} shown in the error message is the PackageCode for MyApp.exe v4.11.
As soon as an msi is referenced a second time within the patch project I get the same "PackageCode {GUID} is not unique" error.
I must be setting this up wrongly but can't what the problem is.
The intention is to have a single patch family that can be deployed to customers on any version and have Windows Installer apply the appropriate patch sequence. Our versioning numbering scheme is to increment the revision number by 10 with each release, e.g. 4.1.10, 4.1.20, 4.1.30, etc and any hot fixes increment by one, so that 4.1.11, 4.1.12 and 4.1.21 are all hot fixes. I'd planned to have a patch family to patch from one version to the next, so there would be a patch to go from 4.1.10 to 4.1.11, then another patch to go from 4.1.11 to 4.1.12, then a patch for 4.1.12 to 4.1.20, then 4.1.20 to 4.1.21 then finally a patch to go from 4.1.21 to 4.1.30.
The idea with this scheme is that we can make use of Least Privilege User Account patching to upgrade a customer from any version to the latest version by applying the correct sequence of binary delta patches.
Am I thinking about this wrongly ?
Your assistance will be appreciated.
Thanks,
Alastair
FOLLOW US
Get the latest news in Application Packaging