Package Information Page - Optional Package Project

Define the Optional package's general information, such as properties that describe how the package appears to users and dependencies.

Target Package Dependency


The identifier name of the target package.

Publisher ID

The publisher ID of the target package.


Define general information about the package.


The globally unique identifier name for the package.

Display Name

The package's friendly name, that will be shown 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".

Package Integrity

Choose the package's degree of run-time integrity checks and remediation:

  • On
  • Off
  • Default

Supported Users

Indicate whether or not the package is multi-user compliant. This option will be verified throughout the installation process to see if the package can be installed on the machine.

  • Single
  • Multiple

Allow Execution

Indicate whether or not the package's executable is authorized to run.


A path to a file that contains an image. Depending on the scale, the image size can vary.

Size200 x 200 px100 x 100 px75 x 75 px63 x 63 px50 x 50 px


Define the publisher information.

Display Name

A friendly name for the publisher that can be displayed to users.


This field must be identical to the publisher subject information contained in the certificate used to sign the package. 

In order to find out more regarding the Publisher ID, please read our How to correctly set the Publisher ID for a UWP AppX article.


Caution!MSIX packages created for Windows versions prior to Windows 10 are incompatible with migration. Check this page for more details.

Caution!Migration is not compatible with MSIX packages build for neutral architecture.

When this store version is launched for the first time, you should automatically transfer previous user data from the desktop app. This is Microsoft's recommendation so users can seamlessly have everything in place.

Uninstall code

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:


UI level

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.

The user should be notified that the migration process has been completed by using the Show notification option. No matter what the UI level is, the notification will appear.