I mixed MSIENFORCEUPGRADECOMPONENTRULES with MSIUNINSTALLSUPERSEDEDCOMPONENTS
So if i use MSIENFORCEUPGRADECOMPONENTRULES="1" then the patch will fail because of the violation of the rules, which is good but still a little bit late in the process to catch it. MSIUNINSTALLSUPERSEDEDCOMPONENTS does nothing and if i understood it correctly according to http://msdn.microsoft.com/en-us/library/bb736321(v=vs.85).aspx it will remove components added by previous patches. On Tue, Apr 1, 2014 at 10:46 AM, Ilir Bekteshi <ilir...@gmail.com> wrote: > I tried MSIENFORCEUPGRADECOMPONENTRULES briefly without success but i'm > going to try it more. > > However, InstallShield seems to detect these problems for example: > > ISDEV : error Val0001: The file 'readme.txt' with a target of > '[programfiles64folder]\a\readme.txt' appears to have been removed from the > setup, but does not appear in the RemoveFile table. This file will not be > removed from the target machine when an upgrade is run unless the > RemoveFile table has been authored. e:\a\test.msi > Val0003: This setup will perform a MINOR upgrade of the referenced > previous setup e:\a\test.msi > ISDEV : error Val0006: The Component 'Readme_file' identified by > ComponentID '{AB51763E-6ECF-4DA5-935A-43E0F16F9980}' is missing from the > newest version of your setup. You can not delete components and still do a > minor/small upgrade. You must perform a major upgrade. e:\a\test.msi > > Some solution like this would be great. > > > > On Mon, Mar 31, 2014 at 8:28 PM, Phil Wilson <phildgwil...@gmail.com>wrote: > >> 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 >> > > ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
