Define general information about the package including attributes that describe how the package appears to users and prerequisites.
Define general information about the package.
The globally unique identifier name for the package.
A friendly name for the package that can be displayed to users.
A friendly description that can be displayed to users.
The version number of the package. The format is a version string in quad notation, e.g. "Major.Minor.Build.Revision".
Select the level of run time package integrity checks and remediation for the package:
Specify if the package is multi-user compatible. This setting will be evaluated at install time to verify if the package can be installed on the system.
Specify if the executable contained by the package is allowed to execute.
Allow External Content
Check this option to allow the MSIX manifest to reference content outside its package, in a specific location on disk. This option should be used for Sparse packages. For more information about how to create a Sparse Package see this article : How to Create a Sparse Package
Specify whether to create a Framework Package (a type of package that can be used by other packages).
An MSIX framework package should have no application entries defined.
To add an MSIX package as a dependency in another MSIX package you should make sure the MSIX dependency is built as a framework package.
A path to a file that contains an image. Depending on the scale, the image size can vary.
|200 x 200 px
|100 x 100 px
|75 x 75 px
|63 x 63 px
|50 x 50 px
Generate the Logo assets.
The source image used to create the assets.
There are some Windows limitations in the .SVG image support. You can find out more information in this article : Why my SVG image isn't rendered properly?
The path on disk where the assets are created.
Press theto select what are the scales of the generated assets.
The scaling used when creating the generated visual assets.
- Bicubic (Sharper Edges, Highest Quality)
- Bilinear (Sharper Edges)
- Nearest Neighbor (Smoother Edges)
Press thebutton to create the assets.
Define the publisher information.
When selecting a certificate in the Digital signature page, Advanced Installer will try to extract the Subject and store it internally. For MSIX packages with sideloading distribution type, at build time, Advanced Installer will try to synchronize the Publisher ID with this cached Subject. If the cached Subject is empty, the Publisher ID from the manifest (displayed in the Package Information view) will be used instead.
This field will be used for all Microsoft Store MSIX builds and for the Sideloading ones as well, in case the cached subject is empty.
To learn more about the Publisher ID, check out the How to correctly set the Publisher ID for a UWP AppX article.
A friendly name for the publisher that can be displayed to users.
Migration is not compatible with MSIX packages built for Windows versions earlier than Windows 10. For more details see this page.
Migration is not compatible with MSIX packages build for neutral architecture.
Automatically migrate previous user data from the desktop app upon first launch of this store version. This is Microsoft's recommendation so users can seamlessly have everything in place.
This is the actual Upgrade Code of your app.
User data folder
The subfolder containing your app's user data. Based on the following examples, choose one of the default Local or LocalLow folders:
Set the UI level to determine the migration user experience.
- Ask user about data migration - moves the user data and uninstalls any previous versions by prompting every time.
- Automatically migrate user data - the same as above without any prompts.
Use the Show notification option to notify the user when the migration has completed. The notification will be shown regardless of the UI level.
Virtualization settings for the MSIX package.
Enables virtualization for the file system entries of your application.
If file system virtualization is disabled, the file system entries of your application can be accessed by other apps (read and write).
Enables virtualization for the registry entries of your application
If registry virtualization is disabled, registry entries of your application can be accessed by other apps (read and write).