Wilson, Phil wrote: > > 1) The code will be different for immediate and deferred custom actions. > Immediate CAs can get properties directly, deferred ones need to use > CustomActionData. This may be something to do with what you're seeing. > 2) RemoveExistingProducts will work fine after InstallInitialize, but note > the documentation says "and before any actions that generate script", > meaning that it pretty much has be immediately after InstallInitialize. >
Ok, I think I get what's going on with RemoveExistingProducts. Since a deferred custom action generates script, I can't place it before the RemoveExistingProducts if it's scheduled after InstallInitialize. But for the immediate CA's, I'm still a little stumped. In my example, I was calling "cmd.exe /c ren c:\foo\bar baz", which failed when run immediate outside of the InstallIntialize/InstallFinalize barrier. Is it because it simply couldn't get the property values? I thought that could be it, but the log does show the full paths correctly, suggesting that it did read the property values correctly... -- View this message in context: http://www.nabble.com/RemoveExistingProducts-and-Duplicate-GUIDs-tp17655018p17734625.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
