Code is being automatically checked in...

[bleitheiser]

I believe I am having a problem with code being automatically checked in which is causing much frustration since we are working in an environment where multiple people are working on the same code base at the same time.

A user was working in one of our modules and then had to reboot his machine. I then needed to get latest and when I try running the code, I am getting runtime errors. The other developer is working on the module and that is why it is blowing up. He did NOT want this code to be checked in since he is in the middle of working in it, and he never checked it in, but somehow his changes were put back to the source control.

How can we get this to stop happening, this is not the first time this has happened. I am looking at the auto commit feature in the Source Gear Vault Client and it is unchecked. I am looking at the Auto Commit check box when in VS 2005 Tools/Options/Source Control/Plug-In Settings/Advanced and the Concurrent Development Style, all this option IS checked and Grey'ed out.

I am using the Classic Client since I am developing a Web Application.

Thanks!

[Beth]

Have the user check the options set in Visual Studio - Tools - Options - Source Control - Integration Options. There is an option to automatically check in changes when the solution is closed. Is that checked?

[bleitheiser]

Have the user check the options set in Visual Studio - Tools - Options - Source Control - Integration Options. There is an option to automatically check in changes when the solution is closed. Is that checked?

We have that checkbox unchecked. Any other reason this could be happening? It happened again this morning.

Thanks,

Brandon

[Beth]

Can you go to your Vault Tools - Options - Check-In and have the user turn off the option to Auto-Commit After Each Operation. This generally doesn't cause any problems when the user is just editing a file and needing to check it in, but it would be good to rule this out anyway. Once that setting is changed, see if it happens again for the user.

In order for Vault to check in edits, it has to specially have a command sent to it to tell it to check the information.

If this continues, it might be easier to troubleshoot offline where I can take a closer look.