# .rc file messed up after applying win32 version info updater
**URL:** https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135
**Category:** Discussion
**Created:** [March 6, 2009, 6:22am UTC](https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135 "2009-03-06T06:22:55Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [March 6, 2009, 6:22am UTC](https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135/1 "2009-03-06T06:22:55Z")
Hi everybody,
We are facing a problem when we try to modify the version of vc++ 2005 project executables. Our main project consists of large number of vc++ 2005 projects. We use 'win 32 version info updater', to change the fileversion/productversion of executables. It has worked fine for all, but two the projects. In case of these two projects, the .rc file is corrupted after the execution of above mentioned action.
For example: Before applying the action,
_VS\_VERSION\_INFO VERSIONINFO
FILEVERSION 1,0,0,1
PRODUCTVERSION 1,0,0,1
FILEFLAGSMASK 0x3fL
#ifdef \_DEBUG
FILEFLAGS 0x1L
#else
FILEFLAGS 0x0L
#endif
FILEOS 0x4L
FILETYPE 0x2L
FILESUBTYPE 0x0L
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904B0"
BEGIN
VALUE "CompanyName", "\0"
VALUE "FileDescription", "SITABpmSendObj Module\0"
VALUE "FileVersion", "1, 0, 0, 1\0"
VALUE "InternalName", "SITABpmSendObj\0"
VALUE "LegalCopyright", "Copyright 2007\0"
VALUE "OriginalFilename", "SITABpmSendObj.DLL\0"
VALUE "ProductName", "SITABpmSendObj Module\0"
** VALUE "ProductVersion", "1, 0, 0, 1\0"**
VALUE "OLESelfRegister", "\0"
END
END
BLOCK "VarFileInfo"
BEGIN
VALUE "Translation", 0x409, 1200
END
END_
And after applying the action:
_VS\_VERSION\_INFO VERSIONINFO
FILEVERSION 1,0,0,2
PRODUCTVERSION 1,0,0,2
FILEFLAGSMASK 0x3fL
#ifdef \_DEBUG
FILEFLAGS 0x01L
#else
FILEFLAGS 0x00L
#endif
FILEOS 0x4L
FILETYPE 0x2L
FILESUBTYPE 0x0L
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904B0"
BEGIN
VALUE "CompanyName", "\0"
VALUE "FileVersion", "10.0.2\0"
VALUE "FileDescription", "SITABpmSendObj Module\0"
VALUE "InternalName", "SITABpmSendObj\0"
VALUE "LegalCopyright", "Copyright 2007\0"
VALUE "OriginalFilename", "SITABpmSendObj.DLL\0"
VALUE "ProductName", "SITABpmSendObj Module\0"
** PRODUCTVERSION 1,0,0,2**
VALUE "OLESelfRegister", "\0"
END
END
BLOCK "VarFileInfo"
BEGIN
VALUE "Translation", 0x409, 1200
END
END_
The version numbers in the output .rc file are expected but as you can see, the format is broken. As a result, following MSBuild action throws these error:
_ERROR RC2133 in .\SITABpmSendMgmtObj.rc(80,0) : unexpected value in value data
ERROR RC2132 in .\SITABpmSendMgmtObj.rc(80,0) : expected VALUE, BLOCK, or END keyword_
This is happening to only two vc++ 2005 projects, in entire build.
Is this some bug or could something be wrong with the projects itself?
Thanking in advance.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [March 6, 2009, 8:55am UTC](https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135/2 "2009-03-06T08:55:10Z")
Hi
I am able to reproduce it here, I’ll post here when we have a build with the fix.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [March 6, 2009, 1:10am UTC](https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135/3 "2009-03-06T01:10:43Z")
Here’s the build with the fix :
[https://www.finalbuilder.com/downloads/finalbuilder/620/FB620\_1359.exe](https://www.finalbuilder.com/downloads/finalbuilder/620/FB620_1359.exe)
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [March 6, 2009, 4:52am UTC](https://www.finalbuilder.com/forums/t/rc-file-messed-up-after-applying-win32-version-info-updater/1135/4 "2009-03-06T04:52:59Z")
Hi Vincent,
That seem to solve the problem. I appreciate your quick response.
Thanks again.
Regards,
Sankalp Shere.