6 replies to this topic

[Superfreak3]

Is there any way of preventing Custom Actions from firing off during an uninstall?  The deferred CAs fire after Register Product on the install.  

They basically call .exe's.  On the remove or uninstall the .exe's are removed which causes the CAs to error and causes a rollback.  I currently have a cheesy little work-around as I have marked the .exe's as permanent then the CAs can fire during uninstall.

Our exe's, which basically update access databases, throw unsightly errors on the screen, however, since the database it is to update has been removed.  It's weak, but prevents a rollback.  This does not always work correctly on 2K boxes though.

Is there any way to clean this up by preventing them from firing at all?  What, if any, condition can I use?

Any help is GREATLY appreciated as I am up against a deadline!

[Ian Blake]

RTFM
Windows Installer
  Installer Database
     Using the Installer Database
        Conditional Statement Syntax

eg.
$ComponentName=3

[Superfreak3]

Is that &ComponentName=3 or $ComponentName=3

[Superfreak3]

Is that &ComponentName=3 or $ComponentName=3

[Superfreak3]

Forget that last one.  I overlooked that bit of info in the link.

Thanks!  I'll let you know!

[Superfreak3]

Thanks Ian!  That worked fine!!!