aweber
Posts: 52
Joined: Mon Jun 18, 2018 7:45 pm

component state not working?

I have a "Launch Installed File" custom action I want to run at the end (or towards the end of the) installation/upgrade/maintenance.

If I leave the "Condition" blank, it will always try to run. It fails if the user did not choose to install the Feature that contains that Component. OK.

However, if I set the Condition to:

Code: Select all

?component_name = 3
(using the condition editor and "Validating" the condition), it does not run on install.

Basically, if the underlying exe file exists, I want to run it. What am I not understanding about component-state 3 ("Installed Locally")?

Thanks,
AJ
Eusebiu
Posts: 4931
Joined: Wed Nov 14, 2012 2:04 pm

Re: component state not working?

Hi AJ,

In order to make sure that the custom action will be executed on install/upgrade/maintenance if a component will be install or if it is already installed, you can use a condition as follows:

Code: Select all

($component_name = 3) OR (?component_name = 3)
Let me know if this helped, otherwise give me more details about your scenario.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”