In this page you can specify the CAB package(s) for your mobile application as well as any other settings required by the Application Manager.
Advanced Installer will automatically generate the Application Manager INI file based on the information you provide. This file appears in the Files and Folders page, is read-only, but can be moved to any folder you want.
A string that will appear in the Application Manager "Add/Remove Programs" dialog's Description field when a user selects the application. This field is required and cannot be left empty.
A string that identifies the application's Windows Uninstall registry key name. This name must match the application's registered Windows Uninstall key name, which is found under the following registry key:
For Windows Installer products, this string is usually the Product Code GUID. Access to this name enables the Application Manager to remove automatically the mobile application from the computer and from the device when the user clicks thebutton in Application Manager "Add/Remove Programs" dialog. Note that the button may not be present, depending on the ActiveSync version the user has installed.
If you want to disable this functionality, leave this field empty.
The name of the mobile application's main executable file. The purpose of this field in the Application Manager INI file is unknown.
These fields are of Formatted Type and can be edited using Smart Edit Control.
This icon appears next to the mobile application in the Application Manager "Add/Remove Programs" dialog. If no icon file is specified, a default icon is used. Choose a file from your project that contains icons by using thebutton and select from the available icons in the drop-down list. Press to use the default icon.
You can specify the CAB package(s) for the mobile application. Providing more than one CAB file allows you to target multiple device platforms.
Make sure the Windows Mobile/CE CAB packages you add in the list are for the same mobile application, with each one targeting a different platform, device type, processor etc. For instance, the CAB packages may have resulted by building an Advanced Installer Windows Mobile CAB Project which contains several configurations.
Adding one or more CAB packages
Use the Ins key while the "Cab Files" list is focused.button or the “Add...” context-menu option or press the
Removing one or more CAB packages
Use the Del key while one or more items are selected in the list control.button, the “Remove” context-menu option or press the
Specifying the order of CAB files in the generated Application Manager INI file
Use the PgUp / PgDown keys while a CAB file is selected in the list control./ buttons, “Up” / “Down” context menu options or press the
The official documentation provides the following guidelines to ensure that Application Manager installs the correct CAB file for the currently cradled device:
- the CAB files targeted at the widest range of platform types and versions must reside at the top of the list, while the CAB files for the most specific platform types and versions will be placed at the bottom of the list.
- the list must also use an order that begins with the newest version and ends with the earliest version.
- if the platform string and version information are specified, information about the WinCE operating system version is ignored.