I created patches as explained further below. All patches contain MSIPatchSequence table. None of the patches are full file updates, they all contain file diff from previous target version. I want P3 to ignore/supersede P2 so that installer eliminates P2 when applying P3.
P1 (v1.0.1) -> Targets RTM (i.e. the major release) -> Provided to all customers. P2 (v1.0.2) -> Targets P1 -> Provided to a select set of customers. P3 (v1.0.3) -> Targets P1 (not P2) -> Expected to be provided to all customers. MsiPatchSequence table for all patches looks as below: PatchFamily = PatchFamilyID ProductCode=”” Sequence = 1.0.3.10000 (for P3), similarly for P2 it is 1.0.2.10000 and for P1 it was 1.0.1.10000 Attributes=1 Ideally, I think it all would have worked if P2 was a QFE but it is not. I cannot change anything in P1 and P2 since they are already released. Question is what can I do in P3 to ignore P2? I have tried putting P2 in ListOfPatchGUIDsToReplace but it is ignored because as per MSDN it only works if P2 did not have MsiPatchSequence Table. I need to Ignore P2 because a fix that was contained in P2 is now part of P3 (which targets P1). When applying P3 over P2 Error 1328 is encountered because P3 contains file diff from P1 but when P2 is applied it changes the file and windows installer can no longer apply the diff contained in P3. Can someone help me regarding this? Thanks ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
