Managing Versioned and Non-Versioned Files
- Aktualisiert2025-07-23
- 2 Minute(n) Lesezeit
Versioned files are binary files that include a version resource, such as executables, DLLs, or LabVIEW packed project libraries. Non-versioned files are text files, such as .ini files, or binary files that do not include a version resource, such as VIs.
MSI-based Installers use the version resource of a file to determine what action to perform when the file already exists on the computer, as shown in the following table.
| Version Resource of MSI-based Installer File | Version Resource of File on Computer | Action MSI-based Installer Performs |
|---|---|---|
| Later | Earlier | Overwrites file on computer |
| Earlier | Later | Does not install the file |
| Any | None | Overwrites file on computer |
| None | Any | Does not install the file |
| None | None | Uses creation and modified dates |
If you update the version of a file, you do not have to use the Force File to Install option on the Distributed Files tab of the TestStand Deployment Utility to include the file in the deployment.
MSI-based Installers evaluate the creation and modification dates of non-versioned files to determine what action to perform when the file already exists on the computer, as shown in the following table. Right-click a file in Microsoft Windows Explorer and select Properties from the context menu to view the modified and created dates.
| Modified Date of File on Computer | Created Date of File on Computer | Action MSI-based Installer Performs |
|---|---|---|
| Later than created date | — | Does not install the file (prevents overwriting changes made to the file after original installation) |
| — | Later than modified date | Overwrites file on computer |
| Same as created date | Same as modified date | Overwrites file on computer |