Hello,
Please note that using an .EXE custom action has many drawbacks, since your cannot set a installer property through an .EXE custom action.
We recommend you to 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++.
Then you can go in the
“Custom Actions” page and add a predefined
Launch attached file custom action. 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.
In order to retrieve the value of a property, you can use the
MsiGetProperty function for C++ or
Session.GetProperty function for C#. Please keep in mind that
Deferred custom actions can receive information about the installation process, mostly only embedded in the CustomActionData property. However, this type of custom actions do not have access to installer properties.
- flag if MSI is running in silent mode or with a GUI
Please note that the installer sets the
UILevel property to the level of the user interface.
Please let us know if that helped, otherwise give us more details about your specific scenario.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging