Summary
This article talks about file versioning rulesSynopsis
During run time, MSI setups use Microsoft's MSI engine to install files, create shortcuts, registry keys, etc. Because the MSI engine is the driving force of such a setup, it follows MSI guidelines to update files.
Discussion
There are two different sets of rules that are taken into consideration when updating file: the overwriting of versioned files and the overwriting of non-versioned files. By default, the MSI engine makes sure that a file with the latest version prevails on the system. Thus, to overwrite a versioned file, you must update the version number of that file in your subsequent upgrade. The following are some file versioning rules that the MSI engine follows while updating or overwriting files.
- Versioned File
- If the file version on the target system is the same as that in the setup package, the file is not updated, irrespective of the date.
- If the file version on the target system is older than that in the setup, the file is overwritten.
- If the file version on the target system is newer than the file within the setup, it is not overwritten.
- If the file version on the target system is the same as that in the setup package, the file is not updated, irrespective of the date.
- Non-Versioned File
- If the file on the target system has a later modified date versus created date, it is not overwritten, as it is considered user data.
- If the file on the target system has the same created and modified date, it is overwritten.
- If the file on the target system has a created date that is later than the modified date, it is overwritten.
- If the file on the target system has a later modified date versus created date, it is not overwritten, as it is considered user data.
Additional Information
The default overwriting rules can be overridden by setting the REINSTALLMODE property. For more information on overriding the default rules using the REINSTALLMODE property, see the Windows Installer Help LIbrary topic REINSTALLMODE Property.
For more information on File Versioning Rules, see the Windows Installer Help topic File Versioning Rules.
Related Articles
Build Errors Caused By Windows Installer CAB File Format Limitations 5Number of Views The Windows Installer Service Could Not Be Accessed 4Number of Views Introduction to Windows Installer Upgrade Types 31Number of Views Launch a Batch File With Windows Installer 9Number of Views Windows Installer Error 1907 5Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago