Once again you pedantically pick through my comment without actually offering anything constructive yourself. Do you feel better now? FWIW it would be nice if you applied your own comment to programs like HEAT because when I saw run a heat harvest command and get a JIT exception, that's certainly not the behavior that I'm looking for in a tool that's supposed to make life easier not harder.
Information, Warning, Error... pick one. I pick error because if the installer consumed a file that is no longer there you need to know about it. You could have a configuration setting that declares the event as a warning and automatically implements the punctured components pattern but I think that assumes too much that the missing file is correctly missing. --- On Wed, 7/23/08, Bob Arnson <[EMAIL PROTECTED]> wrote: > From: Bob Arnson <[EMAIL PROTECTED]> > Subject: Re: [WiX-users] Merge Module Help > To: [EMAIL PROTECTED], "General discussion for Windows Installer XML > toolset." <wix-users@lists.sourceforge.net> > Date: Wednesday, July 23, 2008, 10:33 AM > Christopher Painter wrote: > > This would be a pretty easy scenario to handle. Check > the WXS against the XML and if a component is missing, throw > an error and suggest the puncture component pattern ( > transitive=true condition=false, 0 byte files for storage > ) > > > > "Throw an error" isn't the kind of automation > most people are looking for. > > -- > 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
