Any tips on using Subversion with .net project files?

We just switched from TFS to SVN, and we still love it.

However, he did introduce some new problems.

One way to process project files (.vbproj). The .vbproj file, of course, always changes as files and links change, and if several people encounter conflicts, conflicts will occur.

Oddly enough, in TFS we never had to deal with managing these conflicts, this part was automatically processed. Now in SVN, we iterate over XML in the merge tool, and there have already been some errors.

How do you deal with this? Any tips?

EDIT: By the way, we are using VisualSVN.

+3
source share
7

SVN * proj - / , , .

, .

.sln .vbproj, .suo, .

+5

, .

, , , "mine before theirs". .

, . , . , .

+1

, * proj file + - + . .

+1

, ? .vbproj svn: mime-type , "text/" Subversions .

VSS , . mime .

+1

VisualSVN. TortoiseSVN, Subversion Visual Studio. svn: ignore , . .

+1

AnkhSVN. 2. .suo .., VS 2008, !

+1

, Toroise. , ive .vbproj, diff.

id use _svn instead of .svn, for several reasons, I can’t remember why now with my head, but "." caused me grief.

make sure that you do not run the .user and .suo files, otherwise you will continue to get VS settings for the project, annoying!

You can also get client attachments for VS, such as ankh and visual svn, and only used ankh for bits, but it was a bit slow, but that was probably my PC error.

0
source

Source: https://habr.com/ru/post/1699135/


All Articles