>> I'm surprised that Heat doesn't have the functionality of leaving the >> existing GUIDs in place. I just presumed I wasn't seeing how to do it. > > There was (is?) a project called "Paraffin" (http://xrl.us/mnhwj) for > managing GUIDs. I've never used it so I can't vouch for it, but it may > be what you're looking for. >
Hm. On re-reading that article it appears that Paraffin doesn't actually manage your GUIDs. You could accomplish something custom for your app using heat.exe and a database of some sort. It's definitely a missing part of the toolset. Where I work, teams that deal with large numbers of components just do major upgrades all the time. We figured that we would cross the GUID bridge when we had to for patches. ------------------------------------------------------------------------- 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
