Application Settings
Project:The MSIX Applications view is available in the following project types:
| • | MSIX |
The settings for an application are organized into the following main categories in the Applications view:
| • | Appearance |
| • | Behavior |
| • | Tile Update |
| • | Package Support Framework |
Use MSIX Application’s Appearance settings to specify details such as the Display Name, Description, Visual Asset, Supported Rotations, Content URI, and Declaration Set for the application.
|
Setting |
Project Type |
Description |
||||||||||||
|
Display Name |
MSIX |
Enter the name of the application as it should appear on the target system. This should be a string between 1 and 256 characters in length. |
||||||||||||
|
Description |
MSIX |
Enter a description of the windows app. This should be a string between 1 and 2048 characters in length that cannot include characters such as tabs, carriage returns and line feeds. |
||||||||||||
|
Visual Asset |
MSIX |
Specify Visual Asset name to be associated with the application. Visual elements of this application are retrieved from selected visual asset name in Visual Assets view. |
||||||||||||
|
Supported Rotations |
MSIX |
Describes the orientations in which the app would prefer to be shown for the best user experience. On a device that can be rotated, such as a tablet, the app will not be redrawn for orientations that are not specified here. For instance, if the app specifies only Landscape and LandscapeFlipped orientations, and the device is rotated to a Portrait orientation, the app will not rotate. Important: The devices that can't be rotated, an app might be shown in that device's default orientation and the app's preferred orientation will be ignored. However, on a device with a rotation lock activated, your app's preferred rotation will still be honored. This attribute can have one of the following orientation:
|
||||||||||||
|
Content URI |
MSIX |
Specify Content URI name to be associated with the application. Content URIs for this application are retrieved from selected Content URI Set in Content URIs view. |
||||||||||||
|
Declaration Set |
MSIX |
Specify the Declaration Set name to be associated with this application. Declarations for this application are retrieved from the selected Declaration Set defined in the Declaration view. |
Use MSIX Application’s Behavior settings to specify details such as the key name, target and entry point.
|
Setting |
Project Type |
Description |
|
Key Name |
MSIX |
The unique identifier of the application is within the package. This value is sometimes referred to as the package-relative app identifier (PRAID). The ID is unique within the package but not globally. There may be another package on the system that uses the same ID. The same ID cannot be used for more than once in the same package. This string contains alpha-numeric fields separated by periods. Each field must begin with an ASCII alphabetic character. You cannot use these as field values: "CON", "PRN", "AUX", "NUL", "COM1", "COM2", "COM3", "COM4", "COM5", "COM6", "COM7", "COM8", "COM9", "LPT1", "LPT2", "LPT3", "LPT4", "LPT5", "LPT6", "LPT7", "LPT8", and "LPT9". Enter a key name for the application. |
|
Target |
MSIX |
The default launch executable for the app. This file must be present in the package. This should be a string between 1 and 256 characters in length that must end with ".exe" and cannot contain these characters: <, >, :, ", |, ?, or *. It specifies the default executable for the extension. If not specified, the executable defined for the app is used. As an alternative to manually entering a value, you can click the ellipsis button (...) to browse to the application target. |
|
Entry Point |
MSIX |
The activatable class ID, such as “Office.Winword.Class”. Default is 'Windows.FullTrustApplication' for Windows applications. |
Describes how the app title receives update notifications.
|
Setting |
Project Type |
Description |
|||||||||||||||
|
Recurrence |
MSIX |
The recurrence interval for tile update notifications. This attribute can have one of the following values:
|
|||||||||||||||
|
URI Template |
MSIX |
The URI template for tile update notifications. |
The Package Support Framework is an opensource kit that helps you apply fixes to your existing win32 application when you don't have access to the source code, so that it can run in an MSIX container.
It helps your application follow the best practices of the modern runtime environment. It contains an executable, a runtime manager DLL, and a set of runtime fixes to a package.
In InstallShield 2019 R2 and later, you can now use the Package Support Framework that contains runtime fixes such as the File Redirection Fixup and Custom Fixup in MSIX.
Describes how to apply runtime fixes to a package.
|
Setting |
Project Type |
Description |
||||||||||||
|
Fixup Type |
MSIX, Basic MSI |
Specifies the supported Package Support Framework types by the application. To add a Fixup Type, click Add Fixup Type button. Supported Fixup Types are:
|
||||||||||||
|
Architecture |
MSIX, Basic MSI |
Specifies various architecture options for Package Support Framework to apply fixes. Based on this selection, the application will pick up the runtime files. Select the type of architecture validation that you want to use at the build time. Available options are given below:
|
||||||||||||
|
File Redirection Fixup |
MSIX, Basic MSI |
You can use the File Redirection Fixup to redirect attempts to write or read data in a directory that isn't accessible from an application that runs in an MSIX container. For example, if your application writes to a log file that is in the same directory as your applications executable, then you can use the File Redirection Fixup to create that log file in another location, such as the local app data store. The sample location path is given below: C:\Program Files (x86)\InstallShield\2021\Samples\Package Support Framework\File Redirection Fixup |
||||||||||||
|
Executable |
MSIX, Basic MSI |
Enter the name of the redirection fixup parameter executable name. By default, this field is populated with the primary process name. If the redirection fixup parameter executable has multiple processes, one specific process runs the file redirection, and you can enter a name for that executable in this field. Important:The executable name is case sensitive. Only enter a name for this executable if you are certain of the executable name that is responsible for the file-redirection. If you are not certain, you can get the executable name by running the Process Monitor application (procman.exe). You can enter .*, if you have common file redirection properties to be applied for all the added applications. |
||||||||||||
|
Base |
MSIX, Basic MSI |
Specifies the path where redirection has to be applied. It can either be a known folder which can be selected from the given list of known folders or path which is relative to package root directory. It can be empty if you want to redirect to any directory relative to package root-level. For MSIX and Basic MSI:
For Basic MSI:
|
||||||||||||
|
Patterns |
MSIX, Basic MSI |
File type patterns for which redirection has to be applied. An array whose values are expected to be the values of a type string, each of which gets interpreted as a regular expression for matching the paths relative to the base + relative path. Examples:
|
||||||||||||
|
Custom Fixup |
MSIX, Basic MSI |
Custom redirection fixup will solve application compatibility issues based on the custom fixup details provided by custom json configuration file. The sample location path is given below: C:\Program Files (x86)\InstallShield\2021\Samples\Package Support Framework\Custom Fixup |
||||||||||||
|
JSON Path |
MSIX, Basic MSI |
Specifies custom json configuration file which contains details about custom fixup to be applied on the application including dll details. For MSIX, add custom fixup dlls in the package root level or place them under below directories based on x86 or x64 architecture: For Basic MSI, place custom fixup dlls under below directories based on x86 or x64 architecture:
|
For more information on Package Support Framework, Click here.