Creating Windows App Packages

InstallShield 2020

Project:Windows App creation is available in Basic MSI projects.

Important:The Windows 10 Anniversary Update is required for installing and testing a Windows App package (.appx) with desktop extensions (Desktop Bridge) included. In addition, InstallShield must be installed on a Windows 10 machine or a machine with the Windows 10 SDK installed in order to: digitally sign the Windows App package, utilize Windows App logo variants (described in Windows App Logo Considerations, or to build localized Windows App packages.

The Windows App package (.appx/.msix) format is the simple and secure packaging format used to distribute and install apps on Windows 8.x and 10 and is the only format allowed for Universal Windows Platform apps. Benefits of Windows App packages include:

•

High availability, reliability, and durability, resulting in applications that operate continuously without failure for extended periods of time

•

A smooth installation experience through static builds that require minimal configuration and no customizable UI

•

The option to sell or provide the application through the Windows Store

•

The ability to leverage UWP functionality such as live tiles as well as the ability to utilize UWP APIs

•

The only package format with native support on Windows Nano Server

InstallShield supports creating the Windows App package format and its desktop and server extensions and also provides testing to help you identify items unsuitable for the Windows App package format. When you select a release in the Releases view, a per-release tab titled Appx/MSIX includes settings to create a Windows App package. Here, various core settings can be specified that impact the Windows App package build process.

Windows App packages can be localized using the settings in the Display Properties area on the Appx/MSIX tab. The supported languages used for the Windows App package build match those in the UI Languages settings on the Build tab of the release, as long as MakePRI.exe (within the Windows 10 SDK) is found on the build machine. If MakePRI.exe cannot be found on the build machine, InstallShield will only generate a Windows App package in the default language.

The following instructions provide details on how to create a Windows App package.

To convert a Basic MSI project to Windows app package (.appx) format:

Open the Basic MSI Project that you want to build a Windows App package for as part of building the .msi release.

In the Releases explorer, under the product configuration, click the name of the release for which you want to build a Windows App package.

Click the Appx/MSIX tab and in the Build Windows App Package setting, specify Yes.

Select the Package Type as Appx or MSIX or Both.

Do the following:

•

Use the General area on the Appx/MSIX tab to specify core settings that impact the build process such as choosing whether to include desktop extensions or server extensions.

•

Use the Package Identity Overrides area on the Appx/MSIX tab to uniquely identify the package to Windows.

•

Use the Display Properties area on the Appx/MSIX tab to identify the package to an end user.

For descriptions of these settings, refer to the Appx/MSIX Tab for a Release topic.

To configure tiles created in the Windows App package, open the Shortcuts view and configure settings in the Windows App Package Tile Overrides area. For descriptions of the Windows App Package Tile Overrides settings, refer to the Shortcut Settings topic.

Build the release.

To scan the .msi package for signs of items that are unsuitable for the Windows App package format, run the InstallShield MSIX/UWP App Suitability Suite. On the Build menu, point to Validation, and then click InstallShield MSIX/UWP App Suitability Suite. For more information, refer to the InstallShield MSIX/UWP App Suitability Suite topic.

For information about how to deploy the Windows App package, refer to Deploying Windows App Packages.

Creating Windows App Packages

InstallShield 2020 Help Library

June 2021