Issue 1: When multiple people use TFS Source code Manager, it often results in inconsistent source code within the same file, overwriting other people's code.
Solution:
assigning different development tasks to multiple individuals ensures that the files that are modified by everyone do not overlap.
But there are situations where you can't prevent multiple people from modifying a file at the same time.
Even if more than one person modifies a file at the same time, generally does not change the method in a file at the same time, in the object-oriented language we often add a method, as long as the check-in merge when the mind will not have too many problems.
If more than one person modifies the same method in the same file, pay attention. Either the assignment above the problem, or the class method design is problematic, it is recommended to consider the cohesion of the method.
Question 2: I get the whole solution, why compile less files?
Solution:
A after adding several files and checking in to the center, B opens the entire solution in the morning and compiles it to find that there are no files included.
Here TFS is different from Git, TFS is a central node, and when we check in the new file, we find a hook in front of the VS2013 solution icon that indicates that there is a modification not checked in, because the solution has changed after several new files have been added to the local solution, but the solution is not checked in.
It is often our practice to designate a master programmer to check in a solution at a specific time, and others to only get the latest solution without checking in.
The above mentioned time can try to communicate the development progress of the same day in the first half hour after work, then we check in once, then the master programmer is responsible for collating and checking in the whole solution.
Team Foundation Server source code management usage experience for multi-person development