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
- :
- Re: VerGetFileVersion under Vista
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 18, 2008
10:15 AM
VerGetFileVersion under Vista
Hi,
I'm using VerGetFileVersion to determine the version of a file on the target system. (Installscript-Project).
Problem: under Windows-Vista, this function returns -1 and an empty version string. According to the Installshield documentation -1 is no valid return value of VerGetFileVersion. It seems that the problem has nothing to do with UAC - it occurs on either activated and deactivated UAC.
How can I determine the version of a file under Windows Vista?
H.
I'm using VerGetFileVersion to determine the version of a file on the target system. (Installscript-Project).
Problem: under Windows-Vista, this function returns -1 and an empty version string. According to the Installshield documentation -1 is no valid return value of VerGetFileVersion. It seems that the problem has nothing to do with UAC - it occurs on either activated and deactivated UAC.
How can I determine the version of a file under Windows Vista?
H.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2008
02:33 PM
The path string of the file had quotation marks "c:\...". This worked fine on OS's other than Windows Vista. In order to apply the VerGetFileVersion-function on a Windows Vista OS, the path string has to be without quotation marks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2010
05:07 PM
Thanks for posting this. But what a nightmare having to find out that THIS peculiar function behavior was the probable cause of things hanging in an IS2008 installer on Vista.