If the main package is installed silently, the UI is not spawned, therefore there isn't any "Install" button. A feature-based prerequisite is installed right before the main installation, when you press the "Install" button in the UI. The problem here is the prerequisite sequencing. No, there isn't any difference between when the custom action is executed during a silent / full UI installation. Is there a difference between silent and not silent installation? What I don't understand is, at which time the custom action is executed. In this case, the prerequisite will be installed as a post-install prerequisite (see the case above)Ĭould you please let me know if you are in any of the scenarios above? the prerequisite is of feature-based type and the main setup runs silently.the prerequisite is of post-install type, then the custom action might execute before the installation of the prerequisite, meaning that the config file is not present on the machine when the custom action executes.There might be the case when the file is not present on the machine when the custom action runs. from what I can see, the config file is not from your main package, it is a config file for a prerequisite of yours - PostgreSql. When running the script after installing the setup, you use the exact same path? If so, then this point can be ignored.Ģ.
From what I can see, you give a hard coded path to the config file. make sure that the provided path to the config file is correct. However, this type of custom actions do not have access to installer properties.At a first glance, the custom action seems correctly configured.ġ. Please keep in mind that Deferred custom actions can receive information about the installation process, mostly only embedded in the CustomActionData property. In order to retrieve the value of a property, you can use the MsiGetProperty function for C++ or Session.GetProperty function for C#. Also, the source file will be embedded in the MSI file but will not be deployed at install time with the other application files. This type of custom action can execute an application (EXE or DLL) or run a script (VBScript or Java script).
Then you can go in the “Custom Actions” page and add a predefined Launch attached file 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++. EXE custom action has many drawbacks, since your cannot set a installer property through an.
0 kommentar(er)
