View Single Post
  #3  
Old 07-15-2010, 11:45 AM
mbrock mbrock is online now
Registered User
 
Join Date: 08-05-2009
Posts: 9
Problem versioning split resource files

We have some unmanaged C++ projects that aren't versioning properly. The reason for this appears to be the fact that the rc files for these projects are split into two. The first rc file has an include for rc2, and it's the rc2 file that actually has the versioning information. If these rc files are merged back into 1 rc file, then the versioning works as expected.

My question is this: how is VBP updating these rc files? In the previous release of our product, we were using VS2008 and VBP version 6. In that release, we still had the split rc files, but yet the versioning worked just fine. It was only after converting our VS2008 projects to VS2010, and upgrading to VBP version 7 that the versioning of our C++ DLLs with the split rc files stopped working.

I went back to VBP version 6, and the versioning still didn't work, so I'm thinking it's more something in the conversion to VS2010 that caused it to break.

Any thoughts?
Reply With Quote