[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Visual Studio.NET 2002/3 Best Practices

From: Arild Fines <arild.fines_at_broadpark.no>
Date: 2004-03-20 16:35:25 CET

Brian Beaudet wrote:
> When adding a solution and related projects to a central repository used
> several developers, what are the files (*.sln, *.projdata, *.nunit, etc.)
> that should not go into it? I'm assuming some files are best left
> un-versioned as they are only useful to a particular developer.

You should avoid versioning .suo, .pdb, .projdata, *proj.user, .exe, .pdb
and .obj files. VS.NET will usually put an exclusive lock on the .projdata
and .suo files, causing any Subversion operation on them to fail if the
solution is open in the IDE. The Ankh FAQ briefly touches on this[1].

Putting the .sln and .*proj files under version control is usually
enough(plus the source code, of course).

[1] http://ankhsvn.tigris.org/faq.html#XSLTsection129120121120

AnkhSVN: http://ankhsvn.tigris.org
Blog: http://ankhsvn.com/blog
IRC: irc://irc.freenode.net/ankhsvn
"We've got to find out what people want from fire, how they relate to it,
what sort of image it has for them.' The crowd were tense. They were
expecting something wonderful from Ford.`Stick it up your nose,' he
said.`Which is precisely the sort of thing we need to know,' insisted the
girl, `Do people want fire that can be fitted nasally?'"
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 20 16:35:40 2004

This is an archived mail posted to the Subversion Users mailing list.