Product: FinalBuilder 4.1.0.256
OS: fails on Windows 2000
(but it works on Windows XP!)
Action: Win32 Version Info Updater using a Win32 Version Info PropertySet:
- MajorVersion
- MinorVersion
- ReleaseVersion
- BuildVersion
- CompileDate
updating some VS.NET 2005 Resource Files (*.rc):Updating property : MajorVersion - to : 11
Updating property : MinorVersion - to : 0
Updating property : ReleaseVersion - to : 0
Updating property : BuildVersion - to : 6
Updating property : CompileDate - to : 2006.07.27.09.49
Updating property : CompileDate - to : 2006.07.27.09.49
Error Parsing File : Unexpected FILEVERSION on line : 85
Here are the resource file contents:
VS_VERSION_INFO VERSIONINFO
FILEVERSION 11,0,0,5
PRODUCTVERSION 11,0,0,5
FILEFLAGSMASK 0x17L
#ifdef _DEBUG
FILEFLAGS 0x01L
#else
FILEFLAGS 0x00L
#endif
FILEOS 0x4L
FILETYPE 0x1L
FILESUBTYPE 0x0L
BEGIN
BLOCK “StringFileInfo”
BEGIN
BLOCK “040904b0”
BEGIN
VALUE “CompileDate”, “2006.07.27.09.49\0”
VALUE “FileDescription”, “Application\0”
VALUE “FileVersion”, “11.0.0.5\0”
VALUE “InternalName”, “Application\0”
VALUE “LegalCopyright”, “Company © 2006\0”
VALUE “OriginalFilename”, “Application.exe\0”
VALUE “ProductName”, “Application\0”
VALUE “ProductVersion”, “11.0.0.5\0”
END
END
BLOCK “VarFileInfo”
BEGIN
VALUE “Translation”, 0x409, 1200
END
END
Strange thing is that line 85 is this one:
VALUE “FileDescription”, "Application\0"
The problem is that our nightly builds now keep failing all the time because that dedicated machine is Windows 2000 and the script was developed on a Windows XP (where it works perfectly). Mapping the source data (resource) through a network mapping and executing FinalBuilder with the same script (but on a Windows XP machine!) works, so it must be a Windows 2000 <> XP thing I suppose.
Also, Visual Studio.NET 2005 has no problems with the resource file, not even on Windows 2000.
Thanks a lot!
Tom.
Hmm, our nightly build PC still had version FinalBuilder 4.1.0.228 and not FinalBuilder 4.1.0.256. With that new version, it seems to parse the resource file correctly. Sorry for any inconvenience…
Hi Tom,
Glad you got it sorted out.
- Angus