Hello,
If you want to set the
[ProductVersion] property as a parameter for your .EXE through the
Argument field from the
Search done by a custom executable criteria then I'm afraid we do not have support for this.
In order to use the
ProductVersion property as a command line parameter for your custom action, you can have a .DLL instead your .EXE and within this .DLL you can set a property based on the return code. You can use a DLL custom action for example, you can create your custom action as
a custom action written in C# or
a custom action written in C++.
You will further use the property which has been set by the custom action as a install condition. In order to achieve that, you can select the
install based on condition option for the
Installation behavior from the
feature properties.
Please note that this scenario is working for the
Feature-Based or
Post-install prerequisites.
To launch your .DLL you can go in the
“Custom Actions” page and add a predefined
Launch attached file custom action
with sequence in the
Wizard Dialogs Stage after the
Searches stage. This type of custom action can execute an application (EXE or DLL) or run a script (VBScript or Java script). Also, the source file will be embedded in the MSI file but will not be deployed at install time with the other application files.
If you have other questions, please let us know.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging