Should .sln be kept out of VSS?

[Ronald S. Cook]

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

 

[David Browne]

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.

No, they should be in VSS. IMO, source control should contain everything
necessary to build, run and deploy the projects. The solution contains
critical information about the project dependencies and build order.

David

 

[Martin Milan]

No, they should be in VSS. IMO, source control should contain
everything necessary to build, run and deploy the projects. The
solution contains critical information about the project dependencies
and build order.

David

I quite agree... I would keep them on the source safe machine, but be
prepared to have your own editable copies that you replace everyone once
in a while. That's what I tend to do anyway...

Martin

 

[Guest]

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.

Definately in VSS or any source control system. You need the solution to
load up the projects!

Any reason you do not want the solution in there?

 

[Jay B. Harlow [MVP - Outlook]]

Ronald,
I too am in the keep the .sln files in VSS! camp. As David pointed out they
contain project dependencies & build order information. Especially during
initial development of multi-project solutions.

However as Martin points out, it can be advantageous to create temporary
smaller solutions when you are working on an isolated corner of your
project.

For single project solutions I don't see an immediate value of keeping its
solution in VSS. However I would question most single project solution...