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 description that can be displayed to users.
A friendly name for the package 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".
This attribute describes the architecture of the code contained in the package. It can have one of the following values:
A path to a file that contains an image. Depending on the scale, the image size can vary:
|Size||90 x 90 px||70 x 70 px||50 x 50 px|
Define the publisher information.
This field must match the publisher subject information of the certificate used to sign a package.
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.
Declare the minimum operating system and software requirements that must exist for the package to be applicable to the system.
Minimum Required OS Version
The minimum version of the operating system that the package requires.
Maximum Tested OS Version
This value should be set by the developer with the highest version of Windows that the package was tested on. Windows will not block installation of the package on versions of the OS higher than the value provided.
When an app is executed, Windows will compare this value to the actual OS version as follows:
- If the value is less than the current OS version, Windows may provide behavior compatible with the highest tested OS version for some or all APIs.
- If the value is greater than or equal to the current OS version, Windows will not apply any compatibility changes to APIs.
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.