Appx/MSIX Tab for a Release

Specify whether you want a Windows app package (.appx/.msix) to be built as part of building this release.

Available options are:

Choose a distribution method for your Windows app package. This setting directs which set of warnings are issued for potential problems related to Windows Store policies or requirements related to sideloading. Available drop-down options are:

Optionally, specify the app's minimum supported Windows version number. If you leave this blank, the minimum version number of Windows 10 Anniversary Update is assumed.

The version must contain only numbers and it requires four parts using the following format (with values in each part ranging from 0 to 65535): majorversion.minorversion.buildnumber.revisionnumber, such as:

1.0.0.60325

Use as few characters as possible. For example, do not use unnecessary leading zeros; instead of entering 14.00.25.1, enter the following:

14.0.25.1

Choose whether to include Windows Server extensions as part of the core Windows App package (.appx/.msixWindows App) format, thus creating a Windows Server App. If you want to target Windows Server Nano's installation package format and deploy a service, WMI provider, event source, or performance counter, you should enable server extensions.

If you select No, warnings are issued for any items that cannot be represented.

If you select Yes, additional subsettings can be configured as needed to specify the minimum Windows Server operating system and maximum tested Windows Server operating system supported by the included apps.

Tip:When using InstallShield to create a Windows App package, choose to include either desktop extensions or server extensions, but not both. Although a Windows App package can contain both desktop and server extensions, targeting one set over the other is a more likely scenario.

Optionally, specify the app's minimum supported Windows version number. If you leave this blank, the minimum version number of Windows 7 SP1 Update (6.1.7601.0) is assumed.

The version must contain only numbers and it requires four parts using the format of majorversion.minorversion.buildnumber.revisionnumber (with values in each part ranging from 0 to 6553).

Select the retail or debug build of the C++ runtime that matches the one used in your product.

Note:This setting does not cause the dependency packages to be installed in sideloading scenarios. For those scenarios, the dependency may have to be delivered manually. Also, the debug versions of the of the C++ runtime are only useful for internal testing and cannot be uploaded to the Windows Store. For local testing or sideloading, you may also have to deploy the framework package that is included in the Windows 10 SDK.

Specify App Installer file location.

The App Installer file can be hosted in a shared location like a HTTP endpoint or a UNC shared folder or a local file share, and includes the path to find the MSIX packages to be installed. Users install the app from the shared location or from the web and enable periodic checks for new updates.

Specify the Uri to the app package location. The Uri specified for AppInstaller File URL will be considered if this option is empty. Other information of the MainPackage element, which includes name, publisher, and version can be changed using Package Identity Overrides section mentioned in this page. Information provided in Package Identity Overrides will be considered during build time for both MSIX package and App Installer file as all these information must match with the information included in the manifest of the MSIX application package.

Specify whether you want to configure update settings for this package during app launch. This behavior during OnLaunch shows the UI and is further configurable with the support of HoursBetweenUpdateChecks, ShowPrompt, and UpdateBlocksActivation child attributes as explained below.

Specify whether deployment will show a prompt or not, informing the user about the update. Available in Windows 10, version 1903 and later.

For latest updates, refer to Microsoft documentation.

Specify whether or not to check for updates in the background regardless the app is lunched or not. A check is made every 8 hours independently of whether the user launched the app. This type of update cannot show UI. Choose 'Update Settings on App Launch' for displaying the interactive UI before update process gets triggered. Available in Windows 10, version 1803 and later.

Specify a unique alphanumeric string that identifies your Windows App package to Windows. If this is left blank, InstallShield generates a name based on the Product Name setting in the Product Configuration or General Information.

Specify the string that users will recognize as the name of the package. This is typically the name of the application. If nothing is specified, the Display Name is copied from the Product Name setting in General Information or Product Configuration.

When you type a value for this setting, you are creating a string entry and setting its initial value for all of the languages that are currently in the project. As an alternative to typing a new value, you can click the ellipsis button (...) in this setting to select an existing string. For more information, see Using String Entries in InstallShield.

Note:Localization of Windows App packages requires the Windows 10 SDK be installed on the same machine as InstallShield. If it is not present, InstallShield will build a Windows App package containing only the default language.

Optionally, specify a description to help distinguish the package to an end user.

When you type a value for this setting, you are creating a string entry and setting its initial value for all of the languages that are currently in the project. As an alternative to typing a new value, you can click the ellipsis button (...) in this setting to select an existing string. For more information, see Using String Entries in InstallShield.

Note:Localization of Windows App packages requires the Windows 10 SDK be installed on the same machine as InstallShield. If it is not present, InstallShield will build a Windows App package containing only the default language.