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.
One TFS
Several Projects
Many .cs files…
Many Software Engineers
Many Checkins for all projects which are being developed at the same time.
Some projects ends earlier, and must be deployed, but some of the projects are not completed yet.
What we do, we comment the code parts which are belong to the incompleted projects
Are there any method better to manual methods on TFS 2008
You need to look at your branching strategy before you end up with a trainwreck… See here for a good guide. Each disparate release should have a branch. There is a small amount of extra effort merging code between branches but it will result in you having a repeatably testable “main” branch for each release. Also look at how you’re cutting labels and how your continuous integration is set up (of instigate it if you don’t have any currently).