Deploying Windows App Packages
InstallShield 2020
Edition:Windows App package 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. To digitally sign the Windows App package, InstallShield must be installed on a Windows 10 machine or a machine with the Windows 10 SDK installed.
Tip:Sideloading must be enabled for a Windows App package to be successfully sideloaded. For more information about sideloading, refer to the Enable your device for deployment MSDN article.
The following table provides an overview of the ways you can distribute Windows App packages:
|
Distribution Method |
Description |
Distribution Method Setting |
Signing Considerations |
|
Windows Store |
Upload the Windows App package to the Windows Store. Refer to the Packaging Windows Apps (MSDN article) for more information. Any package distributed through the Windows Store is subject to additional policies that limit its contents. |
Windows Store |
This type of app doesn't need to be signed before it is uploaded to Microsoft because Microsoft signs the package. |
|
Sideloaded and added to a Suite/Advanced UI Project |
Add a sideloading Windows App package to a Suite/Advanced UI project as described in Adding a Sideloading Windows App Package (.appx | .msix) to a Suite/Advanced UI Project. A common example of a sideloading app is one that is distributed to an enterprise environment and is internal to a company only. You can use condition checks such as the Windows App Package Eligible eligibility condition of a Windows App package (.appx) or the UWP Type Present condition in either an exit condition or a package's eligibility condition as well as other condition checks to employ this type of distribution method. This type of scenario provides flexibility to let end users conditionally install an .msi package versus a Windows App package. For more information, refer to the Types of Condition Checks in Advanced UI and Suite/Advanced UI Projects topic. |
Direct Distribution (Sideload) |
If a package will be sideloaded and added to a Suite, the Windows App package must be signed before it is built into the Suite/Advanced UI project. |
|
Sideloaded and delivered as a Windows App package (.appx) |
Deliver a Windows App package (appx) file to your customer as an executable installer that can be double-clicked to perform the installation. A common example of a sideloading app is one that is distributed to an enterprise environment and is internal to a company only. |
Direct Distribution (Sideload) |
If a package will be sideloaded, you will typically need to sign it, unless your customer wishes to sign it themselves. The package must be signed before the double-click installation will succeed. |
See Also
Types of Condition Checks in Advanced UI and Suite/Advanced UI Projects
Adding a Sideloading Windows App Package (.appx | .msix) to a Suite/Advanced UI Project