Chris Bardon wrote:
Ah, I think I solved it. Moved the tag from the InstallExecuteSequence section to the InstallUISequence one, and it executed like it was supposed to. Is there a convention for where these types of things should go? I want to populate some property values from an included XML file before installing, and I was thinking about putting the customaction before AppSearch. Are there any reasons not to do this?
Custom actions should be scheduled in both sequences, usually. If a CA is scheduled only in InstallUISequence, it won't work when a user does a quiet (or quieter) setup, like with /qb or /qn. One option is to mark the CA as Execute="firstSequence" so it only runs once (e.g., in the UI if both sequences are run) if it takes a long time to run.
-- sig://boB http://bobs.org
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
