On 1/25/07, Mike Dimmick <[EMAIL PROTECTED]> wrote:
...
For best results, you should ensure that any common files are members of
the same component (i.e. have the same component GUID) in all packages
that distribute them. Further, the component should have the same
composition (*exactly* the same files, registry keys, shortcuts, etc) in
all packages. The best way to ensure this is to use the same source for the
component every time, and upgrade it carefully. If you need to include this
in any non-WiX Windows Installer package, you'll need a merge module, but
for composing solely WiX packages, it's easier to use a WiX Fragment.
If you can't abide by the rules to keep the component compatible (in both
a semantic sense and in its composition) you must change the GUID *and*change
where it installs to (either its name or the destination directory).
If you don't do this you may suffer the problems described in Rob's blog
post "Component Rules 101" at
http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx
.
...
Thanks Mike, that was very helpful.
One follow-up question regarding the composition of a Component. The
"rules" say to only have one .exe, .dll, or .ocx per component. I'm not
sure what the motivation is for that in the case of non-shared files, e.g.
non-COM DLLs. It certainly makes the WiX source a lot uglier to manage. So
I wonder if it's a rule that can be safely bent.
Scott
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
