Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve seen quite a few visual studio solutions where the actual solution file is not bound but the projects are bound to source control.
Question:
Is there any benefit in this approach when it comes to building on an integration server?
So far I’ve taken the approach that it must have been an oversight and just bound the solution, then committed to source control.
if you are working at the same product/project in a team and everybody needs to get latest, modify and check in changes, the solution file .sln should also be committed or other people will be unable to retrieve it.
user specific files like solutionname.suo do not need to be checked in because every user locally has his/her settings and this should not be persisted in the TFS server.
if the solution file is not checked-in and a developer adds a new project inside a solution, other developers will get the new project but will need to add it manually in their local solution file.
we check in projects and solutions with nornal results. did this in SVN, Mercurial, TFS, always same pattern and always satisfied.