![]() ![]() Here's another example of common functionality: You may want to discard or accept user input depending on whether it meets certain criteria. Or you may want to modify or add some content to a file, but only if it is needed (you don't want to duplicate configuration settings). For example, maybe you need to copy certain files only if the target platform is Mac or Linux, but not if it is Windows. The installation of your application does not have to be a rigid, linear sequence of actions. 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. Creating an installer is not as straightforward as most people think.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |