The custom action will run again. For data driven custom actions that modify machine state, the custom action should decide what to do (create, delete, update) based on the action state of a Component. This is important because in repair you could have Components in all action states: none, install, uninstall.
The WiX custom actions that modify machine state all behave this way. You might take a look at them. On Mon, Dec 27, 2010 at 5:17 PM, Sean Farrow <sean.far...@seanfarrow.co.uk>wrote: > Hi: > I am currently in the process of writing custom actions. When the user > installs a package, a custom action is run to compile a source file to > binary. > What I'm wondering is what happens when the customer repairs the install, > what actions does windows installer perfvorm to determine what need to be > done? > Regards > Sean. > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, > and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
