Previous | Next | See Also

Use this tab to manage the settings related to packaging your Desktop (AIR) application.

Note that this tab is available only if the target platform of the build configuration is Desktop (AIR) and the output type is Application.

ItemDescription
Application descriptorSpecify the application descriptor to be used:
  • Generated. An auto-generated descriptor will be used.
  • Custom template. The descriptor generated according to the specified template will be used.

    To use an existing template, click browseButton (Shift+Enter) and select the template file in the dialog that opens.

    To create and use a new file, click Create. In the Create AIR Descriptor Template dialog that opens, specify the descriptor file properties and click Create.

    When the template is used for generating the application descriptor (e.g. during the compilation or packaging), the text in the <content> element is replaced with the name and extension (.swf) of the application file.

Package file nameSpecify the name of the resulting package file.
Files and folders to package In addition to the application SWF file, you may also want other application assets to be packaged. If so, specify the locations of these additional assets.
  • Path to file or folder. Edit the absolute path to the file or folder where the desired asset resides. Use browseButton (Shift+Enter) to select the file or folder in the corresponding dialog.
  • Its relative path in package. Specify the relative asset location in the package.
  • add (Alt+Insert). Use this icon or shortcut to add another asset to the list. Select the asset location in the dialog that opens.

    Note that for assets within the module source roots, their relative locations in the package, by default, will be set the same as in the source folder. That is, for a file <src>\images\my_icon.png, its relative location in the package, by default, will be images\my_icon.png.

  • delete (Alt+Delete). Use this icon or shortcut to remove the selected item or items from the list.
Use temporary self-signed certificate Select this option to sign the package with a pre-installed self-signed certificate. Otherwise, specify the settings related to signing the package (see below).
Keystore file Specify the path to the keystore file. (This is where a private key and corresponding certificate are stored.)

Type the path in the field or click browseButton (Shift+Enter) and select the keystore file in the dialog that opens.

(If your keystore type is PKCS12, your keystore file, most probably, has the .p12 extension.)

Keystore type Specify your keystore type. The default value PKCS12 corresponds to a keystore file with the .p12 extension.
More options or Less optionsClick the link to show or hide the options described below.
Key aliasSpecify the key alias.

Note that the alias is not necessary if the keystore contains only one key.

Provider classSpecify the Java Cryptography Architecture (JCA) provider for the specified keystore type.
TSA (time-stamping authority)Specify the URL of an RFC3161-compliant time-stamp server to time-stamp the digital signature.