It just goes to show how easy it is to commit gross component rules
violations even after months of reading articles and blogs on component
rules! 

However, it seems that I have also misunderstood the purpose of
MSIENFORCEUPGRADECOMPONENTRULES property. I was under the impression
that it would add to verbose log. I mean, if MSI *knows* that there is
component violation, it would be of great help if it could add a
sentence to the log saying at least something along the lines of:
There is component rules violation of some sort!

After reading all that I could find on MSIENFORCEUPGRADECOMPONENTRULES
property I can't say that I am 100% sure about what is it that it really
does? How can the consequences of having this property defined or not be
seen on some practical example? I was certainly none the wiser in this
specific case since verbose logs were identical with or without it, for
all that I could see.

It *seems* that a small update patch may be applied by MSI in some cases
even if there was a component rule violation and this property prevents
it. 

-----Original Message-----
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: Saturday, August 02, 2008 1:10 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:
> 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"
:) 
>   

Sorry, it's not that polite.<g> The "Windows Installer Components" topic

summarizes the magic of component rules with two bullets:

    In brief, these rules are:

        * Each component must be stored in a single folder.
        * No file, registry entry, shortcut, or other resources should
          ever be shipped as a member of more than one component. This
          applies across products, product versions, and companies.

So changing the directory violates 50 percent of the component rules.<g>

-- 
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

Reply via email to