This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- How many "digits" does Windows Installer check for executable files?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 10, 2011
08:35 AM
How many "digits" does Windows Installer check for executable files?
I know that Windows Installer checks only the first 3 "digits" of a version number for MSI's to determine if an MSI can upgrade over a previous one. That's for MSI's themselves.
Within the MSI, for the version numbers on binary executable files, .exe, .dll, and such, does it also still only check the first 3 "digits" of the version, or does it check all 4 "digits", when deciding if a versioned executable file is a newer version and to replace it or not during an upgrade?
Thank you.
Within the MSI, for the version numbers on binary executable files, .exe, .dll, and such, does it also still only check the first 3 "digits" of the version, or does it check all 4 "digits", when deciding if a versioned executable file is a newer version and to replace it or not during an upgrade?
Thank you.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 10, 2011
05:57 PM
File comparisons use all four a.b.c.d fields.
(The "File Table" help topic describes the data type used for versioned files, and the "Version" help topic describes the xxxxx.xxxxx.xxxxx.xxxxx [each field ≤ 65535] format.)
(The "File Table" help topic describes the data type used for versioned files, and the "Version" help topic describes the xxxxx.xxxxx.xxxxx.xxxxx [each field ≤ 65535] format.)