Bob Arnson-6 wrote:
>
> Immediate custom actions don't run elevated, so if you're testing on
> Vista, it won't have permissions to write to per-machine areas of the
> drive, like Program Files.
>
I'm suspecting that could be the case. I'm not installing on Vista (this is
a server class produc
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 Instal
I've resolved this by attacking it a little differently. I've prevented
from removing the logs directory by setting the
log directory create component to Permenant. Given this, I can now sequence
RemoveExistingProducts after InstallFinalize.
I preserve my config files now as a conditional compon
Rob Mensching-2 wrote:
>
> When is your custom action getting run? If it isn't deferred, then it may
> be running before the other actions have executed or it may not have
> permission to do what it needs to do (because immediate isn't elevated).
I've set RemoveExistingProducts to run after Ins
* BUMP *
Anyone got any ideas her? I'm stumped...
--
View this message in context:
http://www.nabble.com/RemoveExistingProducts-and-Duplicate-GUIDs-tp17655018p17671619.html
Sent from the wix-users mailing list archive at Nabble.com.
5 matches
Mail list logo
