I'm using Vault 2 with VS.NET 2003, not integrated together. Sometimes I'll do the following:
check out file
edit file
build solution
run
check file in
And then a message pops up saying something about some other process having the file and it can't be checked in or something to that effect. Then the file in Vault is not checked out, the status is renegade and the changes haven't been put into Vault.
Anyone else have this problem?
I am using VAX with VS.NET 2003 too if that makes a difference. When I check in the file isn't even open in the editor. This happens about 1 in 30 check ins. My solution is to check it back out, but to pick do not overwrite, then check the file back in.
Instant renegades
Moderator: SourceGear