views:

188

answers:

1

So we have Team Foundation Server running in replacement of our old SourceSafe for about a couple of months now and I've just had the first serious fallout. Just the same what was regularly happening all the time with the SourceSafe.

I check in a file, its content arrives only partially into repository. The rest is got lost on the way.

This time I alone was working on the file. So no interim check-ins by other colleagues. Also no conflicts reported. About half of the file is missing, all that I have implemented today until the lunch time.

What's wrong with it? It's way more expensive than SourceSafe. Why doesn't it work proportionally better?

+2  A: 

When you check a file in it checks the file from the disk in, not what is currently being shown in the IDE, so if you haven't saved the changes it won't check in your changes.

This is the same as with the msbuild process, which is why there is an option to save the files before building in VS. It's because the compiler and the source control are external applications that are being called from the IDE.

uzbones