VS 2003 + Vault 2.02 = random renegades?

EricGHarrison · Post by **EricGHarrison** » Wed Dec 15, 2004 1:51 pm

On occasion VS.NET 2003 will allow us to edit a file that hasn't yet been checked out, and it won't even try to check it out. Instead it becomes a renegade. Unfortunately this does not appear to be consistent. Sometimes, when you try to edit a file, it will prompt you to check it out as it should.

This happens on 2 out of the 3 machines we have using Vault. The one other machine always prompts for the check out.

Does anyone have any suggestions on where to start to try to figure out what's happening?

Thanks! - Eric.

dan · Post by **dan** » Wed Dec 15, 2004 1:58 pm

Check the Visual Studio Source control options - there is an option in there that controls what to do when starting to edit a file, and it may be that on those two machines, they are set to not attempt a file checkout.

EricGHarrison · Post by **EricGHarrison** » Wed Dec 15, 2004 2:17 pm

Thanks for the quick reply Dan!

The setting is:
"Prompt for check out" when checked in items are edited

The "Allow checked-in items to be edited" is not checked. Same as the system that it is working correctly on.

Any other ideas?

dan · Post by **dan** » Wed Dec 15, 2004 3:47 pm

Another idea: Check the read-write permissions on the files themselves. If they are already read-write, VS might think they don't need to be checked out.