Thorsten Albers
7/18/2011 11:05:00 PM
-mhd <not_real@invalid.com> schrieb im Beitrag
<kqa9275kqkd8n5vc4jut68rafp64evfdq3@4ax.com>...
> I know that and that doesn't address the question I asked.
No one can tell you the difference of 'file version' and 'product version'
of a specific DLL except the developer(s) of the DLL (at least one has to
assume that they can).
Often the 'file version' and the 'product version' give the same value. For
some DLLs specific to or shipped with a certain version of Windows/MS
product (like e.g. IE, WMP) MS sets the 'product version' to the Windows/MS
product version number, i.e. the version number of the product with which
the DLL was distributed.
And you should have asked "What is the difference the 4 properties?" -
because actually there are 4 properties:
1. file version (numeric; part of the VS_FIXEDFILEINFO in the file's
version resource; shown at the top of the file version property page)
2. file version (string, part of the file's version resource, may be
localized)
3. product version (numeric; part of the VS_FIXEDFILEINFO in the file's
version resource; >>not<< shown on the file version property page)
2. product version (string, part of the file's version resource, may be
localized)
Although the file version string (product version string) should give the
same version number as the file version number (product version number) in
the VS_FIXEDFILEINFO, this is not necessarily the case. E.g. the file
version number of the COMCTL32.DLL in \WINDOWS\System32 on my WinXP SP3 is
5.82.2900.6028 while the file version string is 5.82
(xpsp_sp3_qfe.100823-1643).
To sum it up: The only version number that really matters is the numeric
file version number in the VS_FIXEDFILEINFO.
--
Thorsten Albers
gudea at gmx.de