In this tab, you can configure a Microsoft APPX/MSIX package which you can use to deploy your app on the UWP.
Select the folder where the APPX/MSIX package will be created.
The name of APPX/MSIX file.
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.
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
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.
The URL path of the AppInstaller file. Only https and file:// protocols are supported.
Select how often will Windows check if your application has pending updates.
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.
If 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.