Thanks for the info. I'll see if I can identify the components that I actually care about for triggering the custom actions.
Rob On 02/06/2010 13:58, Bob Arnson wrote: > On 6/2/2010 3:25 AM, Rob Hamflett wrote: >> I'm seeing some behaviour I don't understand. If you modify an >> installation, but don't actually add >> or remove any features, then I thought nothing happened. If I delete a >> folder before the modify, >> then the installer repairs it. I'm not seeing anything in the log thought >> that indicates why this is >> happening. > > See InstallValidate logging for what MSI plans to do. >> How would I detect that the installer is actually doing something? I have >> conditons based on a >> feature being installed (&feature=3), a feature being removed (&feature=2) >> and a feature being >> repaired (REINSTALL>< "feature"). This all works pretty well, but not for >> this instance. Would I >> have to have conditions based on the components instead? >> > > Yes, custom actions should be declarative and use component states like > all the MSI actions. Features are just convenient collections of > components; when it comes to installing/repairing/etc, MSI works on the > component level. > ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
