I don't believe that there is way to patch creation enforce the MSI rules. They might vary based on the version of Windows Installer you end up using when the patch is installed.
Have you tried MSIENFORCEUPGRADECOMPONENTRULES when you apply the patch? --------------- Phil Wilson On Mon, Mar 31, 2014 at 6:47 AM, Ilir Bekteshi <ilir...@gmail.com> wrote: > Hi All, > > I'm left with not much hair on my head these last couple of days trying to > figure out the MSP problems i'm having. > > This is my scenario: > 1st build: Build full installation (baseline), i use heat directory > 2nd build: Build full installation and Patches using PCP/Msimsp.exe > These work fine, i can apply patches without any issue > > Here is the issue: > 3rd build: A component is added and one is removed and i expect patch build > to fail due to component removal but IT DOESN'T?! It creates patch without > any warning/error. Even when i apply the msp it doesn't complain until i > read the logs that it hasn't patched anything at all. > > My question is how to catch this problem at build time? Shouldn't at the > time i build the Patch complain that a component is removed? > > FYI the strategy is if component changes are necessary then we build a new > baseline and perform a major upgrade then continue with patches until such > scenario occurs. > > A help would really be appreciated. > Thanks > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
