Therefore, the product manual decided that our software should have version numbers with 3 sets of digits, and not the usual 4 (for example, 1.2.3, not 1.2.3.4)
This is easy to do in the About dialog box and elsewhere in the user interface, but I am having problems with Windows properties.
When I change the values ββin the VERSIONINFO block to:
FILEVERSION 1,2,3
PRODUCTVERSION 1,2,3
VALUE "FileVersion", "1.2.3"
VALUE "ProductVersion", "1.2.3"
I will summarize the following in the Windows 7 Properties> Details tab for exe:
File Version: 1.2.3.0 Product Version: 1.2.3
Changing the values ββfor all will be different, indicating that the "File version" is taken from FILEVERSION and therefore is always formatted as a 4-digit group value, but the "Product version" is taken from "ProductVersion".
Is it possible to indicate that the file version should be taken from the string value "FileVersion"? If I delete the FILEVERSION block, I just go back to the βFile versionβ 0.0.0.0.
I reproduced this behavior in VS2010 by creating an empty Win32 console application and then adding a default version resource:
VS_VERSION_INFO VERSIONINFO
FILEVERSION 1,0,1
PRODUCTVERSION 1,0,2
FILEFLAGSMASK 0x3fL
FILEFLAGS 0x1L
FILEFLAGS 0x0L
FILEOS 0x40004L
FILETYPE 0x1L
FILESUBTYPE 0x0L
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "080904b0"
BEGIN
VALUE "CompanyName", "TODO: <Company name>"
VALUE "FileDescription", "TODO: <File description>"
VALUE "FileVersion", "1.0.3"
VALUE "InternalName", "VersionT.exe"
VALUE "LegalCopyright", "Copyright (C) 2012"
VALUE "OriginalFilename", "VersionT.exe"
VALUE "ProductName", "TODO: <Product name>"
VALUE "ProductVersion", "1.0.4"
END
END
BLOCK "VarFileInfo"
BEGIN
VALUE "Translation", 0x809, 1200
END
END
Result in the same release:
properties http://media.use.com/images/s_1/4ba4e5b1b235179b1c9a.jpg
This image may seem small, so I just confirm that it says File version 1.0.1.0 Product version 1.0.4
, , , Windows "FileVersion" ? VERSIONINFO MSDN , .