Should .sln files be kept out of VSS?

Should .sln files be kept out of VSS?

Post by Ronald S. » Wed, 31 Jan 2007 01:20:59


Should Visual Studio solution files (.sln) be kept out of VSS? I'm thinking
so, but want verification before I propose the policy change to my
management.

Thanks,
Ron
 
 
 

Should .sln files be kept out of VSS?

Post by Arni » Wed, 31 Jan 2007 08:46:58


You must have some particular reason in mind but I fail to see
it.

We have solutions with 35+ projects. If I didn't have the
solution in VSS I'd have 35+ individual when refreshing into an
empty directory tree. And, when opening a project, a .SLN file
will be created before it can be saved. So, ???

- Arnie

 
 
 

Should .sln files be kept out of VSS?

Post by Peter Nimm » Thu, 15 Mar 2007 02:18:07


It really depends. A solution is really a high level view of inter-related
projects.

A project cannot exist on its own without being referenced by a Solution -
.sln file. So if you attempt to open a single project then when you close
it or build it then a new .sln file will be created. There is no point
putting these into sourcesafe if that is its only reason for existance. If
on the other hand more than one project is referenced by the solution then
it should of course be put into sourcesafe.

If the project you are putting into sourcesafe is the main controlling
project (say an exe that will refer to libraries either static or dynamic)
then put the .sln file into SourceSafe. If it is a standalone project then
put the .sln file into sourcesafe.

Peter