Chris Ridd wrote: > I'm having some conceptual problems with WIX's <Component>s though, in > particular their GUID attributes. Curiously (for us) Installshield makes > *way* less use of GUIDs than WIX, so my practical problem is how to manage > the $large_number of GUIDs that will be required. Oh yes, 2 * $large_number, > because we're adding 64-bit packages. Joy. >
WiX doesn't dictate GUIDs -- that's Windows Installer. Some authoring tools hide the details or auto-generate them but they're still there. > Some of our packages share Components. It seems clear to me that this means > the GUIDs for the shared Components *must* be consistent across packages for > a given version of all our software. > Correct. Shared components are especially sensitive to following the component rules. > How are Component GUIDs used by the installer during (say) a package > upgrade, or at other times? Do *I* need to remember the GUIDs for all the > Components I'm installing? > If you generate GUIDs every time you build, you won't be able to do any upgrades or patching, except for "full major upgrades." If you pay the price and maintain GUIDs in your WiX authoring that's checked in, you have all the history to do patching and minor upgrades. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
