This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Retrieving a property during deferred execution for a condition
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2008
02:21 PM
Retrieving a property during deferred execution for a condition
Hello,
Okay, so I've been reading on here as well as the help files on getting the value of an MSI property from within a deferred custom action.
However, my requirements are a little different as I want to use the value in a condition with a custom action (launch an .exe).
Has anyone had any experience with this? I need to determine if the .exe should be launched based on what the property was set to during the beginning of the install.
Okay, so I've been reading on here as well as the help files on getting the value of an MSI property from within a deferred custom action.
However, my requirements are a little different as I want to use the value in a condition with a custom action (launch an .exe).
Has anyone had any experience with this? I need to determine if the .exe should be launched based on what the property was set to during the beginning of the install.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2008
02:43 PM
Just use the property as part of a conditional expression for the deferred CA. Conditions are evaluated during the script-generation phase and the proeprty is available for use. If the condition eval's to true then the CA will fire during the deferred phase.
Also if you are directly calling an EXE you can pass the property at the command line because it's evaluated at script generation. When you get into script and dll CA's you have to use the customactiondata property technique.
Also if you are directly calling an EXE you can pass the property at the command line because it's evaluated at script generation. When you get into script and dll CA's you have to use the customactiondata property technique.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2008
03:13 PM
Maybe I wrote my condition wrong then.....for the deferred launch .exe custom action I have the following:
Install Exec Sequence: After InstallFiles
Install Exec Condition: ISPRODUCTINSTALLED = "NO"
If ISPRODUCTINSTALLED was set to "NO" at the beginning of the install then this custom action should run. Doesn't launch though. If I keep the exec condition blank, it will run.
Install Exec Sequence: After InstallFiles
Install Exec Condition: ISPRODUCTINSTALLED = "NO"
If ISPRODUCTINSTALLED was set to "NO" at the beginning of the install then this custom action should run. Doesn't launch though. If I keep the exec condition blank, it will run.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2008
03:16 PM
Run logging and see what it tells you. You might also need to add the property name to the SecureCustomProperties property.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)