Configuration Tab

In this tab, you can configure a Microsoft APPX/MSIX package which you can use to deploy your app on the UWP.

Output

Folder

Select the folder where the APPX/MSIX package will be created.

Name

The name of APPX/MSIX file.

Package

Architectures

Select the target architectures for the package.

  • Create individual packages for each architecture - select to create a different APPX/MSIX package for each architecture selected.
  • Create a bundle with individual packages inside - select to create an APPX/MSIX bundle that can target multiple architectures.

Target Platforms

Select the target platforms for the current build.

  • Desktop - choose the configuration to target for Windows 10
  • Server - choose the configuration to target for Windows Server 2016 / Windows Nano Server 2016

AppInstaller

An AppInstaller is an XML file that contains information about an APPX/MSIX package. It is used by Windows to check for updates to the package and to install them automatically.

URL

The URL path of the AppInstaller file. Only https and file:// protocols are supported.

Frequency check

Select how often will Windows check if your application has pending updates.

Show prompt

Informs the user about the update through a prompt.

Available in Windows 10, version 1903 and later.

Updates block activation

Available only if Show Prompt is checked. Stops the user from launching the application until the update has been installed.

Enabling this option will give the user the option to decide if he wants to install the update or to close the app.

Leaving this option disabled will give the user the option to decide if he wants to install the update or start the app without updating. In this case, the update will be later applied silently

Available in Windows 10, version 1903 and later.

Automatic background task

With this option enabled, periodic checks for updates are made in the background even if the application was not launched. The check for updates interval is 8 hours.

Available in Windows 10, version 1803 and later.

Force update from any version

Enables updating from a higher version to a lower version Without this option, the app can only be updated to a higher version.

Available in Windows 10, version 1809 and later.

Content

Allow UWP specific options

This option allows you to configure the UWP package using Advanced Installer's UI. Settings from the regular MSI-based views/pages will be transferred to the available UWP views if they are supported.

The supported settings that can be automatically transferred are:

  • Application details (Name, Description, etc.)
  • Package description (Name, Logo, Version, etc.)
  • File type associations (File type, Content type, etc.)
  • Visual elements

You can access each UWP specific view by clicking one of the Applications, Visual Assets or Declarations link buttons.

NoteIf you change settings in the UWP views, they will overwrite the settings from the MSI-based views/pages. This means that only the settings from the UWP views will be included in the final build.