Mobile Component - Advanced

Check this box if you do not want to register an uninstaller for your application on the Windows Mobile device. This is not generally recommended.

Note: This option only has effect on Windows Mobile 5.0 and later devices.

Check this box to include a device-side installation DLL in the Windows Mobile installation cabinet. This DLL must be compiled for the CPU architecture of the mobile devices that your application targets (typically ARM or StrongARM), and must contain the predefined entry points Install_Init, Install_Exit, Uninstall_Init, and Uninstall_Exit. For details, consult the Microsoft Windows Mobile SDK documentation.

If you check this box, you must specify the path to the DLL in the text box; you can also click the ... (browse) button to open a standard Windows Open dialog box to browse for the file on your computer.

Note: This option only has effect on Windows Mobile 5.0 and later devices.

Check this box to compress the files inside the Windows Mobile installation cabinet. By default, the files are not compressed.

Note: Compressing the files inside the cabinet is only compatible with Windows Mobile 5.0 and later. Earlier versions of Windows Mobile do not support file compression inside the cabinet. We therefore recommend that you do not use this option. The overall distribution size of your installer is not significantly different anyway, because the Windows Mobile cabinet file itself will be compressed when it is stored in the distribution package.

Check this box to sign the Windows Mobile installation cabinet prior to inclusion in the distribution package. This requires that you have a Windows Mobile-compatible code signing certificate and matching private key; these are typically obtained through the Microsoft Mobile2Market program.

Cabinet signing is optional, but it might affect how your installation cabinet is treated by the installer on the mobile device:

• Unsigned cabinets are treated as untrusted and typically generate a query on the mobile device during installation, leaving the user the choice whether or not to install the application.
• Cabinets signed with an unprivileged certificate can install applications that do not use trusted WinCE API calls. This encompasses the majority of mobile applications.
• Cabinets sign with a privileged certificate can install applications that use trusted WinCE API calls. This is typically used for system-level software such as device drivers.

For details, consult the Microsoft Windows Mobile SDK documentation.

If you check this box, you must configure the Windows Mobile signing options by clicking on Signing options... This is only necessary the first time that you use this option.