General Tab for MSIX Release

Use the Settings view on the General tab to specify core settings that impact the build process such as including desktop extensions or server extensions and signing details.

Describes the architecture of the code contained in the package. A package that includes executable code must include this attribute.

The available codes are given below:

Choose whether to include Universal device extensions as part of the core UWP app package format. If you want to enable your apps to start leveraging Universal Windows Platform (UWP) APIs, you should enable Universal extensions.

If you select,

Optionally, specify the app's minimum supported Windows version number. If you leave this blank, the minimum version number of Windows 10 Anniversary Update is assumed.

The version must contain only numbers and it requires four parts using the following format (with values in each part ranging from 0 to 65535): majorversion.minorversion.buildnumber.revisionnumbe, such as:

Use as few characters as possible. For example, do not use unnecessary leading zeros; instead of entering 14.00.25.1, enter the following:

Choose whether to include Windows Server extensions as part of the core UWP app package format, thus creating a Windows Server App. If you want to target Windows Server Nano's installation package format and deploy a service, WMI provider, event source, or performance counter, you should enable server extensions.

If you select,

Important:When using InstallShield to create a UWP app package, choose to include either desktop extensions or server extensions, but not both. Although a UWP app package can contain both desktop and server extensions, targeting one set over the other is a more likely scenario.

Optionally, specify the app's minimum supported Windows version number. If you leave this blank, the minimum version number of Windows 7 SP1 Update (6.1.7601.0) is assumed.

The version must contain only numbers and it requires four parts using the format of majorversion.minorversion.buildnumber.revisionnumber (with values in each part ranging from 0 to 6553).

Select the retail or debug build of the C++ runtime that matches the one used in your product.

Important:This setting does not cause the dependency packages to be installed in sideloading scenarios. For those scenarios, the dependency may have to be delivered manually. Also, the debug versions of the of the C++ runtime are only useful for internal testing and cannot be uploaded to the Windows Store. For local testing or sideloading, you may also have to deploy the framework package that is included in the Windows 10 SDK.

To customize the Framework Dependencies,

You can use the Msix.xml file, which is installed to the following location:

InstallShield Program Files folder\System

An example is given below:

<VC140 Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.24217.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US">Microsoft Visual C++ 2015 Runtime</VC140>

Specify whether or not you want to sign msix package.

To specify the digital certificate that you want to use to sign your release, click the ellipsis button (...) in this setting. The Certificate Selection dialog box opens, enabling you to specify either the location of the .pfx file, certificate file (EV exported .cer file), or information about the certificate store that contains the certificate.

InstallShield provides an option to encrypt and store an EV token password in the project file using the public key certificate (.cer) file. The .cer file is generally created by exporting a public key from the EV Authentication Client tools associated with a USB eToken provider (for example, SafeNet Authentication Client). InstallShield displays additional options to configure the Extended Validation (EV) certificate properties if the .cer file is specified. For more details, see:

After specifying the .pfx file or choosing the certificate from test store, the below will be displayed:

After specifying the certificate file (EV exported .cer file), the below settings will be displayed:

This read-only setting displays the certificate thumbprint.

This read-only setting displays the certificate's expiry date.

Specify the Private key container name associated to the Cryptographic Service Provider (CSP).

Note:The Container name can be obtained from the Private Key Certificate properties of a user certificate in the EV Vendor Authentication Client tool.

If the .pfx file that you are using has a password, enter it. InstallShield encrypts the password and stores it in your project file (.isl).

At build time, InstallShield uses the password to sign files with a .pfx file. If your certificate is protected by a password but you do not enter it in this setting, signing with a .pfx file fails.

Important:If you configure your project to use a certificate that was imported with password protection into a store, Windows prompts for the password at build time when InstallShield is attempting to sign your project's files. The strong key protection that Windows uses does not permit InstallShield to provide the password to the cryptographic provider.

Specify the signature description that you want to use for files that are specified in.

the Sign Output Files setting. The description that you specify is displayed on the User Account Control (UAC) box to the right of the “Program Name:” label. The UAC dialog box opens when an end user launches the signed file and elevated privileges are required.

If you leave this setting blank, InstallShield uses the name of the file without its extension as the description to the right of the “Program Name:” label on the UAC dialog box. Note that if you use the Sign Files in Package setting and its subsettings to sign the files in your package, InstallShield does not use this signature description for the UAC dialog box of the files in your package that are signed at build time.

Specify a unique alphanumeric string that identifies your UWP app package to Windows. If this is left blank, InstallShield generates a name based on the Package Name setting in the General Information.

Specify the string that users will recognize as the publisher's name. For example:

Revenera

If your customer prefers to sign the package themselves and If nothing is specified, the Display Name is copied from the Publisher setting in General tab.