The Tarma Installer 2 Project - Files page has been renamed to Files and Folders in Tarma ExpertInstall. The overall purpose of the page is still the same: it defines the files and folders that must be installed for your product. However, the folder tree has been changed substantially; see Files and Folders for more information about the new folders tree.
The root node in the Tarma Installer 2 folder tree is called Installation files. In Tarma Installer 2, this node is purely symbolical; it does not have a counterpart on the customer's system. When you select it, the Tarma Installer 2 settings pane shows a number of global file-related settings.
In Tarma ExpertInstall, the root node is called Target System. This Tarma ExpertInstall node represents a real location on the customer's system; it corresponds to the topmost folder on the target system during installation. (This is not normally the installation folder; see Files and Folders for more information about the Tarma ExpertInstall folder tree.) When you select this node it shows the usual folder attributes, which apply only to the Target System node itself.
The following table shows where the settings that were part of the Tarma Installer 2 Installation files node are in Tarma ExpertInstall.
| Tarma Installer 2 | Tarma ExpertInstall | Changes and conversion notes |
|---|---|---|
| Main executable file | n/a |
Tarma ExpertInstall has no concept of a main executable file. In Tarma Installer 2, it had three uses:
|
| Register App Paths | Each installation file can now be registered for App Paths and have an associated paths list. | |
| Application paths list |
Tarma Installer 2 installation folders are always automatically created when required and were deleted once they become empty. In contrast, Tarma ExpertInstall installation folders have explicit installation and removal actions, which allow you to create or delete folders independently from any files installed in them.
The following table shows how Tarma Installer 2 folder settings are converted to Tarma ExpertInstall.
| Tarma Installer 2 | Tarma ExpertInstall | Changes and conversion notes |
|---|---|---|
| Folder name | Folder name | Most folder names are kept as-is, but special folders such as <ProgramFiles> and <WinDir> are converted to folder aliases, and the folder's name is set to a canonical name. Folder names can be localized in Tarma ExpertInstall. |
| (none) | Alias | New in Tarma ExpertInstall; generated automatically for new folders converted from Tarma Installer 2; converted to Tarma ExpertInstall conventions for special folders such as <ProgramFiles> and <WinDir>. |
| Platforms Apply folder settings to |
(none) | Tarma Installer 2 folder platform settings were used to provide default values for any files added to the folder; they did not affect the folder installation proper. In Tarma ExpertInstall, both folder and file installation is controlled by components, and the folder's platform settings are transferred to the component that is created for the folder during conversion. |
| (implicit) | Install action | Set to Create on demand for new folders converted from Tarma Installer 2. This corresponds to the Tarma Installer 2 behavior. |
| (implicit) | Remove action | Set to Remove if empty for new folders converted from Tarma Installer 2. This corresponds to the Tarma Installer 2 behavior. |
Tarma Installer 2 and Tarma ExpertInstall installation files are very similar; the main difference is that in Tarma ExpertInstall file installation is controlled by components, whereas in Tarma Installer 2 file installation was done on a file-by-file basis. As a result, some of the Tarma Installer 2 file settings have been moved to components in Tarma ExpertInstall. Furthermore, file installation and removal actions are more flexible in Tarma ExpertInstall than in Tarma Installer 2.
The following table shows how Tarma Installer 2 file settings are converted to Tarma ExpertInstall.
| Tarma Installer 2 | Tarma ExpertInstall | Changes and conversion notes |
|---|---|---|
| Source path | Source path | No changes |
| Absolute | (none) | You can choose absolute or project-relative paths in the Project Properties - Preferences dialog box. |
| Install as | Install name | Installation name is localizable in Tarma ExpertInstall. |
| Install file if | Install action | Converted to equivalent Tarma ExpertInstall install action; see File installation actions below. |
| Sharing | Shared file | Converted to equivalent Tarma ExpertInstall sharing and removal options; see File removal actions below. |
| Registration | Registration | No changes |
| REG file | (none) | During conversion to Tarma ExpertInstall, external REGEDIT4 files are imported into the Tarma ExpertInstall registry. To ensure that all imported registry keys and values are associated with the installation file and are installed and removed with it, the conversion process creates a separate component for each Tarma Installer 2 file with external REGEDIT4 registration, and assigns both the file and all the imported registry keys and values to that component. |
| Attributes | Attributes | No changes |
| Install | Install action | Converted to equivalent Tarma ExpertInstall install action; see File installation actions below. |
| Uninstall | Remove action | Converted to equivalent Tarma ExpertInstall remove action; see File removal actions below. |
| Reboot | Reboot if installed | No changes |
| Delete | Install action | Converted to equivalent Tarma ExpertInstall install action; see File installation actions below. |
| Platforms | (none) | In Tarma ExpertInstall, file installation is controlled by components and all platform settings, installation conditions, and language selections are transferred to the component that controls the file. If necessary, a new component is created for the combination of settings that the Tarma Installer 2 file required. |
| Cond | (none) | |
| Languages | (none) |
Tarma ExpertInstall file installation actions combine several different Tarma Installer 2 settings. The following table shows how Tarma Installer 2 installation-related settings are converted to Tarma ExpertInstall.
| Tarma Installer 2 | Tarma ExpertInstall | ||
|---|---|---|---|
| Install | Delete | Install file if | Install action |
| Cleared | Cleared | n/a | Do not install |
| Checked | Not present yet | Install if not present | |
| Always | Install always | ||
| Newer | Install if newer | ||
| Already present | Install if present | ||
| n/a | Checked | n/a | Remove |
File removal is similar between Tarma Installer 2 and Tarma ExpertInstall. However, Tarma ExpertInstall handles shared files different from Tarma Installer 2. The following table shows how the various Tarma Installer 2 Uninstall and Sharing options are converted to Tarma ExpertInstall.
| Tarma Installer 2 | Tarma ExpertInstall | ||
|---|---|---|---|
| Uninstall | Sharing | Remove action | Shared file |
| Cleared | Not shared | Do not remove | Cleared |
| Untrusted reference count | Checked | ||
| Trusted reference count | |||
| Checked | Not shared | Remove always | Cleared |
| Untrusted reference count | Remove if installed | Checked | |
| Trusted reference count | Remove always | ||