File attributes

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.

For a detailed overview of the interaction between the file packaging options and those of its component and build configuration, see the Installer packaging topic.

Tip: If you distribute the file in uncompressed (plain) format, you can obtain its source path at installation time through the $srcpath() runtime function. This allows you to refer to the file prior to installation (after installation, you can use the normal <#file_alias> syntax).

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 Tarma Installer 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.

Check this box and enter a semicolon-delimited list of search paths for the file if any App Paths registration must take place for the file; clear it for no App Paths registration.

App Paths registration registers the file name and its location in the Windows registry and optionally adds application-specific search paths that are used when the application loads DLLs.

Check this box and enter the arguments for the file's DllInstall function if the file needs to be registered through its DllInstall entry point; clear it for no additional file registration. This is in addition to the Registration self-registration option.

Enter a number between 0 and 65535 that determines in which order the file will be registered, if its Registration field allows registration. The default registration order number for DLLs is 1000; see File registration for a full list of file registration orders.

When you add a new installation file to your project, Tarma Installer will automatically assign a registration order to the file based on built-in heuristics and detected dependencies. However, not all registration dependencies can be statically detected, so if you know that a particular file must be registered before or after another one, then you can set the file's Registration order field to a lower (before) or higher (after) number than the other's registration order number.

Files are registered by increasing order number and unregistered in the opposite order. If two files have the same Registration order number, their mutual order may vary between installation sessions.

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.

Check this box to let Tarma Installer 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).

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.

Check this box to exclude the file from any installation rollback; clear it to let the file participate in the rollback, if any.

An installation rollback is performed if the installation fails; in that case, any files that were replaced prior to the failure are restored to their original versions. However, this requires additional disk space during installation (to save copies of the original files), so for very large files that are not critical, you might choose to disable the rollback functionality.

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. See File version comparisons for information about "newer" files.

Note: This is the recommended action for Add-on and update installers.

Restores the version of the file that was present before the current product was installed. If no new version was installed (for example, if the pre-existing version was up to date), nothing happens. If there was no pre-existing file at all, the current file is removed as per Remove always.

Restoration of a shared file is subject to its SharedDlls reference count (see above); if this count is > 0 after decrementing, the file is not restored but left as-is. This prevents problems in the sharing products, which might rely on the current version of the file.

Note: This is the recommended action for Add-on and update installers.

1. Compare the ProductVersions (binary). The file with the higher ProductVersion is newer.
2. If both ProductVersions are equal, compare the FileVersions. The file with the higher FileVersion is newer.
3. If the FileVersions are also equal, both files have the same version.

1. The file with the VERSIONINFO resource is newer, regardless of its actual version.

1. The file with the later Modified date is newer.
2. If the Modified dates are equal, both files have the same version.