handling resource files

[Steve Borho]

On Thu, Aug 13, 2009 at 3:13 AM, Colin
Caughie<c.caughie at indigovision.com> wrote:
>> I really like this idea. Sadly, I don't think it will work because
>> the
>> resource.h file that contains all the id definitions is created and
>> modified by Visual Studio (add a control to a dialog, a new id is
>> allocated).
>>
>> I like the idea, so I'm thinking about a step that takes the VS
>> generated resource.h file and renumbers it, but that's getting close
>> to
>> my threshold of too kludgy.
>>
>> I'm actually surprised that this doesn't seem to be much of a
>> problem.
>> Either that, or I'm not searching on the right terms.
>
> Visual Studio resource files are a version control nightmare, there's no getting around it. Our biggest gripe is the way VS 2005 rewrites the string tables in a different order when you edit something completely unrelated; if this happens when there are multiple branches (which there almost always are in our team) the next merge is going to be a major headache.
>
> It's bad enough that I've considered writing a custom merge tool just to merge resource files. If I ever do I'll let you know. :)

Our projects always use XPJ to generate project and solution files
from an XML source.  The .vcproj and .sln files are never checked in.

--
Steve Borho