My team has a recurring problem that drives me crazy. People claim that some checks in Team Foundation Server overwrite previous check-ins / existing code. They claim that you always need to do Get Latest Versionbefore you register. In other words, launching the latest version is a prerequisite for proper registration.
In response, answer as follows: There should be a definition of / t TFSthat we are missing / we did not note if the above described is really happening. What is the point of having a version control system that will not automatically warn you of code conflicts during verification (if before your verification someone else checked in a different code than yours)? I would understand if there were settings that set this or that behavior (check, regardless of what is in the db now, or warn if there are any conflicts and tell me about the action (merging)).
I want to understand: am I mistaken ?! Is this just a way of working TFS? Get Latestis mandatory before any checks, no matter what ?!
As a side note, if checking without manually launching the latest version is risky and dangerous, why won't Microsoft do this by default ?!
Thanks in advance!
source
share