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
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 th
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,
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,
4 matches
Mail list logo
