This can be useful for performing actions or setting environment variables based on the value of the parameter.Įxecutes right before the file copying step starts. This can be useful for changing the value of the parameter before it is displayed.Įxecutes after the corresponding parameter page has been displayed. If any of the actions result in an error, an error message will be displayed to the user and the user will be prompted to enter a valid value.Įxecutes before the corresponding parameter page is displayed. The actions can be used to check that the value is valid (for example, that it specifies a path to a valid Perl interpreter). Note that those actions are not executed if the installer is executed in unattended mode.Įxecutes once the user has specified a value in the user interface page associated with the parameter and has pressed the 'Next' button (or 'Enter' in a text-based interface). It is commonly used for setting user-defined installer variables that will be used later on or for detecting a Java (tm) Runtime Environment.Įxecutes after the component page is displayed to check that the selected components are a valid combination.įor each parameterPage, you can specify 3 different action lists: validationActionList, preShowPageActionList and postShowPageActionList. For multi-platform CDROM installers, the postBuildActionList is executed once for every one of the specific platform installers and then it is executed one final time for the whole CDROM build.Įxecutes before help information is displayed.Įxecutes when the installer has started, just before the parsing of the command line options.Įxecutes before the first page of the installer is displayed, right after the parsing of the command line options takes place. These actions are usually useful to reverse any changes made to the files during the preBuildActionList or to perform additional actions on the generated installer, such as signing it by invoking an external tool. For multi-platform CDROM installers, the preBuildActionList is executed once at the beginning of the CDROM build, and then again for every one of the specific platform installers.Įxecutes after generating the installer file. These actions usually include setting environment variables or performing some kind of processing on the files that will go into the installer before they are packed into it. Action lists include your actions of choice and are executed at a specific point of the installation process as outlined below.īitRock InstallBuilder Action Lists (in order of execution)Įxecutes before generating the installer file. You can place your action lists in the main installer project or in one of its components. It is important to understand how and when each action must be performed, what differences exist between action lists inside components and within the primary installer, how the installer will behave when you run it in different installation modes (GUI, text, or unattended) and what happens when you generate rpm or deb packages. InstallBuilder actions are organized in what are called action lists, which are executed at specific points of the installation process. Actions can be accessed by editing the XML project file directly or in the 'Advanced' section of the InstallBuilder GUI. BitRock InstallBuilder includes a number of useful built-in actions to facilitate adding complex functionality to your installer. You may need to check a registry value, create a configuration file, execute a particular command, make substitutions in text files or even connect to an external server via a HTTP POST request. This is especially the case for more sophisticated configurations, such as when you need to execute different platform-specific actions at different stages of the installation process. This way, you can use a password as an argument in a action and log the execution without showing the plain text password.Creating an installer is not as straightforward as most people think. password suffix is used to mark a variable as a password to be hidden in the logs.
0 Comments
Leave a Reply. |