VC++ 4.2 Version Number Resource

Another team member changed the Version number of our project to 1, 0, 2, 0
using the MSDev Visual Studio resource manager.   When I look at the version number using the resource manager, I get the old version, 1, 0, 1, 0.  Looked at the .rc file using Wordpad, it says 1, 0, 2, 0.  But when I look at the .res files (using the resource manager ) in either the Release or Debug folders, the version number is 1, 0, 1, 0.    Tried saving, build all, quitting and restarting, closing and reopening the project ... without success.  
TBurschAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chensuCommented:
There are two version numbers. One is numbers; another is a string.

VS_VERSION_INFO VERSIONINFO
 FILEVERSION 1,0,0,1                <==== Here
 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", "dlgdll DLL\0"
            VALUE "FileVersion", "1, 0, 0, 1\0"             <==== And here
            VALUE "InternalName", "dlgdll\0"
            VALUE "LegalCopyright", "Copyright (C) 2000\0"
            VALUE "LegalTrademarks", "\0"
            VALUE "OriginalFilename", "dlgdll.DLL\0"
            VALUE "ProductName", "dlgdll Dynamic Link Library\0"
            VALUE "ProductVersion", "1, 0, 0, 1\0"
        END
    END
    BLOCK "VarFileInfo"
    BEGIN
        VALUE "Translation", 0x409, 1200
    END
END
0
TBurschAuthor Commented:
Thank you for the thought, but while you are correct about the version number appearing in two places in the .rc file, the answer did not fix my problem.   I checked the .rc by looking at it with Notepad.  One place says
1, 0, 2, 0, the other 1,0,2,0, but the resource manager still is still reporting 1, 0, 1, 0.
0
chensuCommented:
You might want to try deleting all the intermediate files and rebuilding it.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

TBurschAuthor Commented:
chensu,
Do you mean, delete all of the .obj files and then rebuild?   Is that different than doing a Rebuild All?
It's worth a try.
tom
0
chensuCommented:
>Do you mean, delete all of the .obj files and then rebuild?

Yes, including .res, .aps, .clw, .ncb, .opt, ...

>Is that different than doing a Rebuild All?

It should be the same. But who knows?
0
TBurschAuthor Commented:
Ok, I deleted everything in the Debug and Release folders ( .obj, .srb, .res  files ) and recompiled.   When I look at the version number using the Project Workspace, I still get 1, 0, 1, 0.

But I did notice somthing else.   If I open NT Explorer and double click on the .res file (either one), if Development Studio is running, the resource tree is displayed in the window where source code usually is displayed ( sorry, I don't know what that window is called ) and if I open the Version resource there, it shows
1, 0, 2, 0.  Opening the Version Resource from the Project Workspace still shows the old number.  Don't know where these two windows get data from, but it does seem to be different.

I have searched my drives for other copies of the .res, there are none.
There is only one .rc file in the folder where the source is.
0
chensuCommented:
Open the generated .exe file as a resource to see what version information is inside.
0
TBurschAuthor Commented:
Looked at the properties of both the debug and release version of the executable, both said 1, 0, 2, 0.   Looks like MSDev is screwed up ... everything else agrees.
0
chensuCommented:
So the version information is correctly generated.
0
TBurschAuthor Commented:
Well, yes.   I .exe seems to be getting created correctly.  The properties for the file are correct.   I should have run the executable to see what the Help About says.  I'll do that Monday.

If that is correct, why is it that the Development Studio Resource Manager is still reporting 1, 0, 1, 0?  I can't figure out where that old revision number is comming from.  Could it be comming out of some part or the Registry?   Maybe I dealing with a Dev Studio bug of some kind?
 
0
chensuCommented:
I have no idea.
0
TBurschAuthor Commented:
Check the Help About ... the version number that appears there comes from a .h that we change manually.  The only info from the .res or .rc is the build date, and that look correct.

Searched the Registry for 1, 0, 1, 0   ... found nothing.
We must be close.

0
TBurschAuthor Commented:
Think I found it!  I noticed a couple other problems relating to the Development Studio and reinstalled the v4.2 patch b fixes.  Thought that was done already, but evidently not.  Fixed the other anomalies and now the version number is comming up correctly in the resource manager too.

Thanks for your help, chensu.  Send another comment, I will accept it as the answer.  
0
chensuCommented:
Great!

Thank you.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.