# Applications

install4j BeanInfo catalog. Each entry below documents a bean class that can appear inside a `<serializedBean>` element in an install4j project file.

## Contents

- [Custom application](#custom-application) — `com.install4j.runtime.beans.applications.CustomApplication`
- [Installer](#installer) — `com.install4j.runtime.beans.applications.InstallerApplication`
- [Uninstaller](#uninstaller) — `com.install4j.runtime.beans.applications.UninstallerApplication`

---

### Custom application
- **Class:** `com.install4j.runtime.beans.applications.CustomApplication`
- **Multiple instances:** yes

A custom installer application is installed by the installer. Users can start it manually or it can be executed programmatically from your own code via the API.

| Property | Type | Category | Visible when | Description |
|---|---|---|---|---|
| `executableName` — Executable name | String [context=noInstallerVariables] | Executable | `createExecutable`=true | The name of the executable for the custom application. Please enter a name without any path components and without a file extension. |
| `executableDirectory` — Executable directory | File [context=noInstallerVariables] | Executable | `createExecutable`=true | The directory to which the executable of the custom application will be written. If empty, it will be placed in the .install4j runtime directory. |
| `unixMode` — Unix mode | String | Unix | — | The executable mode for the custom application on Unix. |
| `useCustomMacosExecutableName` — Use custom application bundle name | boolean | macOS | — | If selected, a different application bundle name is used on macOS. Executable names on macOS are localizable. Otherwise, the value of the "Executable name" property is used for the application bundle name. |
| `customMacosExecutableName` — Custom application bundle name | String [context=noInstallerVariables] | macOS | `useCustomMacosExecutableName`=true | The application bundle name to be used for macOS media files. Bundle names on macOS are shown in the Finder and are localizable. For example, the executable name could be set to ${i18n:myLauncherName(${compiler:sys.fullName})} where myLauncherName is an i18n message with value "Launcher for {0}". |
| `createExecutable` — Create executable | boolean | Executable | — | If selected, an executable for this installer application will be created. If not selected, this application launcher can only be invoked with the com.install4j.api.launcher.ApplicationLauncher API or an automatic launcher integration.For macOS single bundles, executables for installer applications are never created. |
| `singleInstance` — Single instance | boolean | Executable | `createExecutable`=true | If checked the application will ensure at startup that there is only one instance running per user account. |
| `windowTitle` — Window title | String | GUI Options | — | The title of the application window. |
| `showCancelMessage` — Show message when user cancels | boolean | GUI Options | — | If selected, a message will be shown when the user cancels the installer application by clicking on the "Cancel" button or closing the application frame. |
| `cancelMessage` — Cancel message | String | GUI Options | `showCancelMessage`=true | The message that is shown if the user cancels the installer application by clicking on the "Cancel" button or closing the application frame. The options that are presented to the user are "Cancel" or "Continue". |
| `changeWorkingDir` — Change working directory | boolean | Execution Options | — | If selected the working directory will be changed to the value in 'Working directory' at startup. |
| `workingDir` — Working directory | File [context=noInstallerVariables] | Execution Options | `changeWorkingDir`=true | The working directory to be used when 'Change working directory' is selected. |
| `vistaExecutionLevel` — Execution level | [VistaExecutionLevel](enums.md#vistaexecutionlevel) | Windows | — | The execution level for this application. If you want to modify files in the installation direction, you most likely need administrator rights. This is only relevant for Windows Vista and higher. |
| `allowUnattended` — Allow unattended mode | boolean | Execution Modes | — | If selected, the user can pass -q as an argument to run the installer application without a GUI. No user input is required, the installer applications work with the default values. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support unattended installations. If your policy forbids unattended installations or if you include custom code that cannot handle unattended installations, you can disable them by deselecting this property. |
| `unattendedProgressInterfaceProvider` — Progress interface creation script | ScriptProperty → UnattendedProgressInterface | Execution Modes | `allowUnattended`=true | If you would like to implement your own way of displaying progress information for unattended installations, you can do so by returning a custom implementation of com.install4j.api.context.UnattendedProgressInterface from this script. If you return null, no progress information will be shown just as if this script had not been set. There is a default implementation com.install4j.api.context.DefaultUnattendedProgressInterface that does nothing for all its operations. You can derive from that class if you just need to implement a few particular methods in the progress interface.If you just need a simple dialog that shows progress information in unattended mode, please choose the "Unattended mode with progress dialog" execution mode instead. |
| `allowConsole` — Allow console installations | boolean | Execution Modes | — | If selected, the user can pass -c as an argument to run the installer application on the console. The installer asks for user input on the console in that mode. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support console installations, form screens are also fully mapped to console installers. If your policy forbids console installations or if you include custom code that cannot handle console installations, you can disable them by deselecting this property. |
| `unixFallbackToConsole` — Fall back to console mode on Unix | boolean | Execution Modes | `allowConsole`=true | On Unix, users often operate in environments where no X11 server is available and no GUI can be displayed. The installer will fall back to console mode if console mode execution is allowed and this option is selected. Otherwise, an error message will be displayed that tells the user how to invoke the installer in console mode. |
| `disableConsoleOnWindows` — Disable console mode on Windows | boolean | Execution Modes | `allowConsole`=true | Offer console mode only on non-Windows platforms. |
| `consoleScreenChangeHandler` — Console screen change handler | ScriptProperty → void | Execution Modes | `allowConsole`=true | By default, a screen in console mode does not show any particular separation. You insert your own custom display with this script. The title parameter gives you access to the title of the screen. In console mode, screens display their subtitle only, so the title string will not be displayed again. |
| `helpCustomizer` — Help customizer script | ScriptProperty → void | General Customization Options | — | If the user starts the installer application with one of the arguments -h -help /?, help regarding the available command-line options will be displayed. If you have your own command-line options, you can customize this help with this script. The script receives a List containing String arrays of length 2 with the options and explanations. You can add options like this: options.add(new String[] {"/mySwitch", "Explanation of mySwitch"}}. You can also delete default options in the list.Attention: The context parameter has not been initialized at that point.In order to get extra command line arguments in the installer, call context.getExtraCommandLineArguments() in any script. |
| `executionMode` — Default execution mode | [ExecutionMode](enums.md#executionmode) | Execution Modes | — | The default execution mode for the installer application. By default, a GUI wizard will be shown, but it is also possible to run in console mode or unattended mode by default. |
| `splashMessage` — Title for progress dialog | String | Execution Modes | `executionMode`=Unattended mode with progress dialog | The title for the progress dialog, for example "Updating installation".This title and the unattended mode with a progress window can also be set by passing -splash [title] as an argument from the command line. |
| `unattendedAlerts` — Show alerts | boolean | Execution Modes | `executionMode`=Unattended mode with progress dialog | By default, no alerts are shown in unattended mode. This includes messages boxes, error alerts and questions. By selecting this property, alerts are enabled for unattended executions with a progress dialog.This mode can also be activated by passing -alerts as an argument from the command line. |
| `windowsConsoleExecutable` — Windows console executable | boolean | Execution Modes | — | If selected, a console executable will be created on Windows. A non-hideable console will be shown when the installer is double-clicked in the explorer. This improves the user experience for a console-only installer (default execution mode set to console) and allows execution through rsh. |
| `frameWidth` — Window width | int | GUI Options | — | The width of the window displayed by the installer application. The default value is 500. If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameHeight` — Window height | int | GUI Options | — | The height of the window displayed by the installer application. The default value is 390.If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameSizeClientArea` — Size client area | boolean | GUI Options | — | If selected, the supplied size for the window will not be applied to the outer dimensions of the window, but to the actually usable area inside the window. Unusually large window frame borders can occur due to user settings (accessibility, window themes, etc.) and may interfere with banner images or introduce unwanted scroll bars to form screens. |
| `resizable` — Resizable | boolean | GUI Options | — | If selected, the window displayed by the installer application is resizable. |
| `vmParameters` — VM parameters | String | Execution Options | — | If you need to pass special VM parameters to the installer application, you can enter them here. A common case would be to raise the maximum heap size with a different -Xmx parameter if your installers require a lot of memory. |
| `arguments` — Arguments | String | Execution Options | — | If you need to pass fixed default arguments to the installer application, you can enter them here. For example, if you want to display a splash screen in unattended mode by default, you can set the arguments to -splash "Installing ...". Please note that command line arguments will be appended to this list, so it is not possible to "override" a fixed argument from the command line. |
| `rollback` — Rollback on failure | boolean | Execution Options | — | If selected, the installer application will try to restore the state before the last rollback barrier by rolling back all actions that were executed since the last barrier. Any screen or action can be selected as a rollback barrier with the property "Rollback barrier". If no rollback barrier was encountered, all executed actions will be rolled back. |
| `customizeVersionInfo` — Customize version info | boolean | Windows | — | If selected, you can customize the fields of the Windows version info in the nested properties. A Windows version info resource is always generated for the executable with default values for product name and file version taken from the general settings. |
| `versionInfoProductName` — Product name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The product name field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoFileVersion` — File version | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file version field in the version resource. If empty, the version from the general settings is used. The file version must consist of four numbers separated by spaces, commas or dots. |
| `versionInfoInternalName` — Internal name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The internal name field in the version resource. If empty, the short name from the general settings is used. |
| `versionInfoFileDescription` — File description | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file description field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoCopyright` — Copyright | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The copyright field in the version resource. If empty, the publisher name from the general settings is used. |

### Installer
- **Class:** `com.install4j.runtime.beans.applications.InstallerApplication`
- **Multiple instances:** yes

The installer is the sequence of screens and actions that are executed when the user invokes the media file.

| Property | Type | Category | Visible when | Description |
|---|---|---|---|---|
| `allowUnattended` — Allow unattended mode | boolean | Execution Modes | — | If selected, the user can pass -q as an argument to run the installer application without a GUI. No user input is required, the installer applications work with the default values. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support unattended installations. If your policy forbids unattended installations or if you include custom code that cannot handle unattended installations, you can disable them by deselecting this property. |
| `unattendedProgressInterfaceProvider` — Progress interface creation script | ScriptProperty → UnattendedProgressInterface | Execution Modes | `allowUnattended`=true | If you would like to implement your own way of displaying progress information for unattended installations, you can do so by returning a custom implementation of com.install4j.api.context.UnattendedProgressInterface from this script. If you return null, no progress information will be shown just as if this script had not been set. There is a default implementation com.install4j.api.context.DefaultUnattendedProgressInterface that does nothing for all its operations. You can derive from that class if you just need to implement a few particular methods in the progress interface.If you just need a simple dialog that shows progress information in unattended mode, please choose the "Unattended mode with progress dialog" execution mode instead. |
| `allowConsole` — Allow console installations | boolean | Execution Modes | — | If selected, the user can pass -c as an argument to run the installer application on the console. The installer asks for user input on the console in that mode. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support console installations, form screens are also fully mapped to console installers. If your policy forbids console installations or if you include custom code that cannot handle console installations, you can disable them by deselecting this property. |
| `unixFallbackToConsole` — Fall back to console mode on Unix | boolean | Execution Modes | `allowConsole`=true | On Unix, users often operate in environments where no X11 server is available and no GUI can be displayed. The installer will fall back to console mode if console mode execution is allowed and this option is selected. Otherwise, an error message will be displayed that tells the user how to invoke the installer in console mode. |
| `disableConsoleOnWindows` — Disable console mode on Windows | boolean | Execution Modes | `allowConsole`=true | Offer console mode only on non-Windows platforms. |
| `consoleScreenChangeHandler` — Console screen change handler | ScriptProperty → void | Execution Modes | `allowConsole`=true | By default, a screen in console mode does not show any particular separation. You insert your own custom display with this script. The title parameter gives you access to the title of the screen. In console mode, screens display their subtitle only, so the title string will not be displayed again. |
| `helpCustomizer` — Help customizer script | ScriptProperty → void | General Customization Options | — | If the user starts the installer application with one of the arguments -h -help /?, help regarding the available command-line options will be displayed. If you have your own command-line options, you can customize this help with this script. The script receives a List containing String arrays of length 2 with the options and explanations. You can add options like this: options.add(new String[] {"/mySwitch", "Explanation of mySwitch"}}. You can also delete default options in the list.Attention: The context parameter has not been initialized at that point.In order to get extra command line arguments in the installer, call context.getExtraCommandLineArguments() in any script. |
| `executionMode` — Default execution mode | [ExecutionMode](enums.md#executionmode) | Execution Modes | — | The default execution mode for the installer application. By default, a GUI wizard will be shown, but it is also possible to run in console mode or unattended mode by default. |
| `splashMessage` — Title for progress dialog | String | Execution Modes | `executionMode`=Unattended mode with progress dialog | The title for the progress dialog, for example "Updating installation".This title and the unattended mode with a progress window can also be set by passing -splash [title] as an argument from the command line. |
| `unattendedAlerts` — Show alerts | boolean | Execution Modes | `executionMode`=Unattended mode with progress dialog | By default, no alerts are shown in unattended mode. This includes messages boxes, error alerts and questions. By selecting this property, alerts are enabled for unattended executions with a progress dialog.This mode can also be activated by passing -alerts as an argument from the command line. |
| `windowsConsoleExecutable` — Windows console executable | boolean | Execution Modes | — | If selected, a console executable will be created on Windows. A non-hideable console will be shown when the installer is double-clicked in the explorer. This improves the user experience for a console-only installer (default execution mode set to console) and allows execution through rsh. |
| `frameWidth` — Window width | int | GUI Options | — | The width of the window displayed by the installer application. The default value is 500. If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameHeight` — Window height | int | GUI Options | — | The height of the window displayed by the installer application. The default value is 390.If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameSizeClientArea` — Size client area | boolean | GUI Options | — | If selected, the supplied size for the window will not be applied to the outer dimensions of the window, but to the actually usable area inside the window. Unusually large window frame borders can occur due to user settings (accessibility, window themes, etc.) and may interfere with banner images or introduce unwanted scroll bars to form screens. |
| `resizable` — Resizable | boolean | GUI Options | — | If selected, the window displayed by the installer application is resizable. |
| `vmParameters` — VM parameters | String | Execution Options | — | If you need to pass special VM parameters to the installer application, you can enter them here. A common case would be to raise the maximum heap size with a different -Xmx parameter if your installers require a lot of memory. |
| `arguments` — Arguments | String | Execution Options | — | If you need to pass fixed default arguments to the installer application, you can enter them here. For example, if you want to display a splash screen in unattended mode by default, you can set the arguments to -splash "Installing ...". Please note that command line arguments will be appended to this list, so it is not possible to "override" a fixed argument from the command line. |
| `rollback` — Rollback on failure | boolean | Execution Options | — | If selected, the installer application will try to restore the state before the last rollback barrier by rolling back all actions that were executed since the last barrier. Any screen or action can be selected as a rollback barrier with the property "Rollback barrier". If no rollback barrier was encountered, all executed actions will be rolled back. |
| `customizeVersionInfo` — Customize version info | boolean | Windows | — | If selected, you can customize the fields of the Windows version info in the nested properties. A Windows version info resource is always generated for the executable with default values for product name and file version taken from the general settings. |
| `versionInfoProductName` — Product name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The product name field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoFileVersion` — File version | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file version field in the version resource. If empty, the version from the general settings is used. The file version must consist of four numbers separated by spaces, commas or dots. |
| `versionInfoInternalName` — Internal name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The internal name field in the version resource. If empty, the short name from the general settings is used. |
| `versionInfoFileDescription` — File description | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file description field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoCopyright` — Copyright | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The copyright field in the version resource. If empty, the publisher name from the general settings is used. |
| `suppressProgressDialog` — Suppress initial progress dialog | boolean | Execution Options | — | If selected, the initial native progress dialog of the installer is not displayed. |
| `createStderrLog` — Create log file for stderr output | boolean | Windows | — | If selected, and output on stderr is detected, a log file will be created and all output to stderr will be redirected to that file. |
| `stderrLog` — Log file for stderr | String [context=environmentVariable] | Windows | `createStderrLog`=true | The log file for the stderr output relative to the installer media file. |
| `languageSelectionScript` — Replacement script for language code | ScriptProperty → String | General Customization Options | — | With this script you can replace the language that the installer will run with. Parameters: The parameter languageCode contains the 2-letter ISO 639 code of the auto-detected language. If auto-detection has not been enabled on the language step of the general settings, the parameter will be null. Return value: If you return null, the language selection dialog will be shown, if you return a language code, the language selection dialog will not be shown, and the returned language will be used. If the returned language code is a language that is not configured for this installer, the language selection dialog will be shown. |

### Uninstaller
- **Class:** `com.install4j.runtime.beans.applications.UninstallerApplication`
- **Multiple instances:** yes

The uninstaller removes the installed application. If you do not wish to provide an uninstaller, you can disable it.

| Property | Type | Category | Visible when | Description |
|---|---|---|---|---|
| `executableName` — Executable name | String [context=noInstallerVariables] | Executable | — | The name of the executable for the uninstaller. Please enter a name without any path components and without a file extension. |
| `executableDirectory` — Executable directory | File [context=noInstallerVariables] | Executable | — | The directory to which the executable of the uninstaller will be written. If empty, it will be placed in the .install4j runtime directory. |
| `unixMode` — Unix mode | String | Unix | — | The executable mode for the uninstaller on Unix. |
| `useCustomMacosExecutableName` — Use custom application bundle name | boolean | macOS | — | If selected, a different application bundle name is used on macOS. Executable names on macOS are localizable. Otherwise, the value of the "Executable name" property is used for the application bundle name. |
| `customMacosExecutableName` — Custom application bundle name | String [context=noInstallerVariables] | macOS | `useCustomMacosExecutableName`=true | The application bundle name to be used for macOS media files. Bundle names on macOS are shown in the Finder and are localizable. For example, the executable name could be set to ${i18n:myLauncherName(${compiler:sys.fullName})} where myLauncherName is an i18n message with value "Launcher for {0}". |
| `allowUnattended` — Allow unattended mode | boolean | Execution Modes | — | If selected, the user can pass -q as an argument to run the installer application without a GUI. No user input is required, the installer applications work with the default values. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support unattended installations. If your policy forbids unattended installations or if you include custom code that cannot handle unattended installations, you can disable them by deselecting this property. |
| `unattendedProgressInterfaceProvider` — Progress interface creation script | ScriptProperty → UnattendedProgressInterface | Execution Modes | `allowUnattended`=true | If you would like to implement your own way of displaying progress information for unattended installations, you can do so by returning a custom implementation of com.install4j.api.context.UnattendedProgressInterface from this script. If you return null, no progress information will be shown just as if this script had not been set. There is a default implementation com.install4j.api.context.DefaultUnattendedProgressInterface that does nothing for all its operations. You can derive from that class if you just need to implement a few particular methods in the progress interface.If you just need a simple dialog that shows progress information in unattended mode, please choose the "Unattended mode with progress dialog" execution mode instead. |
| `allowConsole` — Allow console installations | boolean | Execution Modes | — | If selected, the user can pass -c as an argument to run the installer application on the console. The installer asks for user input on the console in that mode. Please see the corresponding help topic on installer modes for more information. All standard actions and standard screens support console installations, form screens are also fully mapped to console installers. If your policy forbids console installations or if you include custom code that cannot handle console installations, you can disable them by deselecting this property. |
| `unixFallbackToConsole` — Fall back to console mode on Unix | boolean | Execution Modes | `allowConsole`=true | On Unix, users often operate in environments where no X11 server is available and no GUI can be displayed. The installer will fall back to console mode if console mode execution is allowed and this option is selected. Otherwise, an error message will be displayed that tells the user how to invoke the installer in console mode. |
| `disableConsoleOnWindows` — Disable console mode on Windows | boolean | Execution Modes | `allowConsole`=true | Offer console mode only on non-Windows platforms. |
| `consoleScreenChangeHandler` — Console screen change handler | ScriptProperty → void | Execution Modes | `allowConsole`=true | By default, a screen in console mode does not show any particular separation. You insert your own custom display with this script. The title parameter gives you access to the title of the screen. In console mode, screens display their subtitle only, so the title string will not be displayed again. |
| `helpCustomizer` — Help customizer script | ScriptProperty → void | General Customization Options | — | If the user starts the installer application with one of the arguments -h -help /?, help regarding the available command-line options will be displayed. If you have your own command-line options, you can customize this help with this script. The script receives a List containing String arrays of length 2 with the options and explanations. You can add options like this: options.add(new String[] {"/mySwitch", "Explanation of mySwitch"}}. You can also delete default options in the list.Attention: The context parameter has not been initialized at that point.In order to get extra command line arguments in the installer, call context.getExtraCommandLineArguments() in any script. |
| `executionMode` — Default execution mode | [ExecutionMode](enums.md#executionmode) | Execution Modes | — | The default execution mode for the installer application. By default, a GUI wizard will be shown, but it is also possible to run in console mode or unattended mode by default. |
| `splashMessage` — Title for progress dialog | String | Execution Modes | `executionMode`=Unattended mode with progress dialog | The title for the progress dialog, for example "Updating installation".This title and the unattended mode with a progress window can also be set by passing -splash [title] as an argument from the command line. |
| `unattendedAlerts` — Show alerts | boolean | Execution Modes | `executionMode`=Unattended mode with progress dialog | By default, no alerts are shown in unattended mode. This includes messages boxes, error alerts and questions. By selecting this property, alerts are enabled for unattended executions with a progress dialog.This mode can also be activated by passing -alerts as an argument from the command line. |
| `windowsConsoleExecutable` — Windows console executable | boolean | Execution Modes | — | If selected, a console executable will be created on Windows. A non-hideable console will be shown when the installer is double-clicked in the explorer. This improves the user experience for a console-only installer (default execution mode set to console) and allows execution through rsh. |
| `frameWidth` — Window width | int | GUI Options | — | The width of the window displayed by the installer application. The default value is 500. If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameHeight` — Window height | int | GUI Options | — | The height of the window displayed by the installer application. The default value is 390.If the "Size client area" property is selected, this does not include the size of the window frame border. |
| `frameSizeClientArea` — Size client area | boolean | GUI Options | — | If selected, the supplied size for the window will not be applied to the outer dimensions of the window, but to the actually usable area inside the window. Unusually large window frame borders can occur due to user settings (accessibility, window themes, etc.) and may interfere with banner images or introduce unwanted scroll bars to form screens. |
| `resizable` — Resizable | boolean | GUI Options | — | If selected, the window displayed by the installer application is resizable. |
| `vmParameters` — VM parameters | String | Execution Options | — | If you need to pass special VM parameters to the installer application, you can enter them here. A common case would be to raise the maximum heap size with a different -Xmx parameter if your installers require a lot of memory. |
| `arguments` — Arguments | String | Execution Options | — | If you need to pass fixed default arguments to the installer application, you can enter them here. For example, if you want to display a splash screen in unattended mode by default, you can set the arguments to -splash "Installing ...". Please note that command line arguments will be appended to this list, so it is not possible to "override" a fixed argument from the command line. |
| `rollback` — Rollback on failure | boolean | Execution Options | — | If selected, the installer application will try to restore the state before the last rollback barrier by rolling back all actions that were executed since the last barrier. Any screen or action can be selected as a rollback barrier with the property "Rollback barrier". If no rollback barrier was encountered, all executed actions will be rolled back. |
| `customizeVersionInfo` — Customize version info | boolean | Windows | — | If selected, you can customize the fields of the Windows version info in the nested properties. A Windows version info resource is always generated for the executable with default values for product name and file version taken from the general settings. |
| `versionInfoProductName` — Product name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The product name field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoFileVersion` — File version | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file version field in the version resource. If empty, the version from the general settings is used. The file version must consist of four numbers separated by spaces, commas or dots. |
| `versionInfoInternalName` — Internal name | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The internal name field in the version resource. If empty, the short name from the general settings is used. |
| `versionInfoFileDescription` — File description | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The file description field in the version resource. If empty, the full name from the general settings is used. |
| `versionInfoCopyright` — Copyright | String [context=noInstallerVariables] | Windows | `customizeVersionInfo`=true | The copyright field in the version resource. If empty, the publisher name from the general settings is used. |

