Hi, I'm in the process of altering our Windows package building scripts from using Installshield to using WIX. So far (cross fingers) so good.
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. 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. But what's the best way to manage GUIDs for the non-shared Components? I can easily generate them on the fly in our packaging scripts, so this satisfies the basic requirement that they must be unique. But I'm concerned that I'm not recording these GUIDs for posterity. 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? Sorry if this is a dumb question :-) Cheers, Chris ------------------------------------------------------------------------- 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
