I tried using it during patch application like: msiexec /update Patch.msp /lv*x .\install.log MSIENFORCEUPGRADECOMPONENTRULES=1 LOGVERBOSE=1
but reading the install.log I cannot find anything a bit more explicit about this violation. It is certainly not saying something like "you changed the name of your root installation folder and you shouldn't" :) -----Original Message----- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 5:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number? Tony Juricic wrote: > If Pyro is not ignoring 4th version number then it must be that I am breaking some component rules?! > I haven't added or removed or renamed any component file or guid but I have changed the target install directory name from MyProduct to MyProductV1 (to be created under Program Files folder). > > Could that be it? > Yes, that's a component rules violation. You can tell from a verbose log, by setting the MSIENFORCEUPGRADECOMPONENTRULES property to 1. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
