IMHO, when you automate part of the process, you take responsibility for the automation always being correct. To me that means the automation needs to be able to handle all of the scenarios. Patching is one of the scenarios. Run the deduction to the end and you see what a difficult problem the Component/@Guid creates.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 23, 2008 08:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge Module Help Christopher Karper wrote: > FWIW, I personally would rather manage the process by exception, instead of > *always*. > Yes, some help is usually better than none.<g> It's all about managing expectations. If it's possible to automatically generate the original setups, not being able to generate patches might be surprising. -- 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 ------------------------------------------------------------------------- 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
