This field contains the path to where the CABinet package is created. Click on thebutton to change it. By default, this shares the same folder with the project file. Removing the package name will delete the whole path.
The path will be saved relative or absolute, as specified in the Project Paths Tab.
Specify the name of the CABinet package. By default the project name is used.
At the right of the “File Name” text field you can select the extension for the generated CABinet package, from either:
- "cab" - the default package extension which you will use most often.
- "cpf" - or CAB Provisioning Format file which is used for provisioning and configuring Windows Mobile-based devices. A valid .cpf file contains only an XML provisioning setup file and is usually compressed and digitally signed. It is processed similarly to a .cab file, but in silent mode - which means that the user is not prompted for any options or decisions. Use the “Pre XML Path” and/or “Post XML Path” fields from the XML Provisioning tab to specify valid Client Provisioning XML files.
- "tsk" - this extension is used for Pocket PC theme (skin) CABinets.
Compress CAB package
Compress the contents of the CABinet package by means of the MSZIP compression algorithm, in order to significantly reduce its size and download time on a device.
Note that most devices do not support compression and installing a compressed CABinet and will cause the installation to fail. Only SmartPhone devices support CAB compression as well as Pocket PC devices starting from Windows Mobile 5. See the platforms summary page for a comprehensive list of platforms and device types.
Generate binary instruction setup file inside CAB
This is a special file generated by Advanced Installer at build time and it contains installation instructions for the content of the CABinet package (files, folders, shortcuts etc). This is basically an installation script and it is processed by the Wceload tool when the CAB package is launched on a target device. Either this option or the “Generate XML provisioning setup file inside CAB” option from the XML Provisioning tab or both must be selected in order to obtain a valid Windows Mobile/CE CAB package.
The binary instruction setup file is not used on SmartPhone devices, which require the XML provisioning setup file in order to correctly install the CABinet contents. Newer Pocket PC devices (starting from Windows Mobile 5) are able to install XML-based CAB packages, but will also use the binary instruction setup file if the XML provisioning setup file is not present inside the CAB. Older devices (pre-WM 5 Pocket PC devices, Palm-size PC and Handheld PC devices) all require the binary instruction setup file inside the CAB, being unable to read the XML provisioning setup file.
For compatibility with older devices and platforms, you should enable generation of this file. However, if you are only targeting SmartPhone and post-Windows Mobile 5 Pocket PC devices with your application, you can uncheck this option in order to reduce the overall size of the CAB package.
Do not digitally sign the CAB package
This option enables you to override the global “Sign the package” option from the Digital Signature page, by not signing the package. If this option is not selected, the global “Sign the package” option will determine whether the CAB package for the selected configuration will be signed or not.
As with CAB compression, digitally signed CABinets will fail to install on some platforms / device types. As a rule of thumb, if a particular device type does not support compressed CABs, most likely it will not support digitally signed CABs either.
All SmartPhone devices as well as Pocket PC devices starting from Windows Mobile 5 should support digitally signed CAB packages, whereas older devices most likely do not (for instance, Windows Mobile 2003 Second Edition Pocket PCs).
Custom Setup DLL
The full path to a Custom Setup DLL. Click on thebutton to select a new DLL file from your hard drive or the button to clear the existing one.
This article contains sample code and describes the requirements for a custom Setup DLL. As explained in the article, the processor type for the Custom Setup DLL should match the processor type specified for the CAB package in the Target Platforms Tab.