Mobile File attributes

A Mobile File object represents a file for installation on a Windows Mobile device. You can optionally register them if they contain self-registration code.

Installation of a mobile file is controlled indirectly by its Mobile Component: the file is added to the mobile component's Windows Mobile installation cabinet and will be installed whenever that cabinet is installed on a mobile device. The file will be removed whenever its application is removed from the mobile device; this falls outside the control of InstallMate.

Attributes

This pane contains the following attributes and options.

Attribute Description
Install name

Enter the installation name of the file; this is the name under which the file will be installed. By default, it is set to the file name in the Source path, but you can change this if desired. You may use symbolic references in the name, but they will be resolved when the installer is built, not during installation.

File alias Enter the alias for the file. This alias must be unique in the project. InstallMate uses the alias to retrieve the file's installation path using the <#file_alias> syntax.
Source path

Enter the source path of the file (i.e., the path to the file on your own system), or click ... (browse) to open the standard Open dialog box that allows you to select the desired file.

Note: Source paths are always displayed as fully qualified paths. However, by default InstallMate stores source paths as relative to the project file's folder. This allows you to move the entire project to a different location, or to access the project and its contents through a different path, for example through a network share on a shared file server.

To store source paths as absolute paths instead of relative paths in the project file, you must change the project default settings by choosing the File > Properties command from the main menu bar and selecting the Preferences page. The options on this page allow you to change the way the various file paths in the project file are stored.

Tip: To move the project file to a different location without moving its source files, use the File > Save Project As... command from the main menu bar. Do not move the project file itself manually, because that will break the relative paths (if any) in the project file.

Install action Select the desired installation action from the drop-down list. The installation action is executed when the Windows Mobile installation cabinet generated from the file's component is installed onto the mobile device, if any. The following choices are available:
Install action InstallMate
Install if not present The installation file is only installed if it does not already exist. If it is already present on the target system, it is left unchanged.
Install if present The installation file is only installed if it already exists. In that case, the existing file is replaced by the installation file if the installation file is newer than the existing file.
Install if newer If the installation file does not yet exist on the target system, it is installed. If the installation file already exists, the existing file is replaced by the installation file only if the installation file is newer than the existing file.
Install always The installation file is installed and the existing file, if any, is replaced by the installation file regardless of versioning considerations.
Remove action Select the desired removal action from the drop-down list. The removal action is executed when the file's application is removed from the mobile device. The following choices are available:
Remove action InstallMate
Remove always If the installation file exists, it is removed. Note that the actual file removal is still subject to its SharedDlls reference count; see Shared file below for more information.
Preflight check signature

Check this box to let InstallMate check if the file in question has a valid digital signature. Only some file types can be digitally signed (mostly executable files), so this option is typically used to ensure compliance with Windows application guidelines that mandate that all executables of a product have a digital signature.

If this option is checked and the file does not have a valid digital signature, then a BLD:W0155 diagnostic is produced, which by default stops the build process (this is subject to the Treat warnings as errors setting in the build configuration attributes).

Register with DllRegisterServer Call the file's DllRegisterServer entry point to register the file, and DllUnregisterServer to unregister it. This is typically used with in-process COM servers such as ActiveX controls and others.
Archive
Read-only
Hidden
System

Check these boxes to set the corresponding file attribute when the file is installed; clear them to install the file without the corresponding attribute. These attributes are initialized from the source file's attributes, except for Archive, which is always cleared.

Shared file

Check this box to indicate a shared file; clear it for an application-private file.

If you mark an installation file as Shared file, its SharedDlls reference count is incremented when the file is installed. This is true even if the file is not physically installed, for example when the existing version is reused because of versioning considerations.

Conversely, when a shared file is removed its SharedDlls reference count is decremented. The file is only physically removed from the target system if both its SharedDlls reference count is zero and its removal condition is satisfied.

Related topics

Files, Folders, Shortcuts, Working with attribute panes