On Fri, 27 Sep 2002 09:05:42 -0400, bkowald@xxxxxxxxxxx ("Brian
Kowald") wrote:
>
>I too have started adding Visual Studio projects to CVS.I am also using
>CVSNT.
>
>I was wondering what people are doing with visual studio files. Not only
>what files are checked in, but are they checked in as binary or text?
>
>Here is what I am doing with visual studio files:
>
>Files from visual studio to check in as BINARY
>.dsp
>.dsw
>.vpj
>.vpw
>.vtg
No idea what .vpj, .vpw, and .vtg files are - we don't keep these in
cvs, they're probably just temporary files anyway. .dsp and .dsw are
just text files... if two developers decide to add to the same
project (unusual, but it does happen) being able to merge them by hand
is quite useful.
>Files from visual studio to check in as TEXT
>.clw
We don't keep these in cvs - they are temporary files that are easy to
recreate.
> 2.. resource.h could get duplicates due to the fact that two different
>developers could add a resource, and it would use the next number. There is
>a visual studio macro I got at
>http://www.codeproject.com/useritems/orderresid.asp to fix resource.h. Note:
>is hard codes resource.h in lower case, I modified mine to ignore the case.
Allocate resource ranges to your developers, and make sure they stick
to them. The Windows resource ID system sucks... glad they're getting
rid of it. In general conflicts of resources are quite rare, as
multiple developers working on exacrtly the same resources would have
organisational problems anyway.
>
>Any comments - about this or just using CVS for Visual Studio projects in
>general?
>
VS.NET uses .vcproj and .sln instead of .dsw and .dsp. In practice
it's oinly these two files that need to be in cvs for the projects to
work correctly.
Tony
|
