File not checking out properly on edit from IDE

[Noble Bell]

Must be some setting that I am overlooking here...

I am using VS 2005 and Vault client 4.12. I just recently had to reformat my machine's hard drive and reload everything. Since then it seems that when I load a file from a project into my VS IDE the little lock indicating that the file is checked-in is visible on the tab at the top of my editor. I can edit and work on the file like normal but the little lock never goes away and when I am ready to check the file back in there is is no "check in" option only a "checkout" option. I can check out the file, check it back in, and all my changes are there. How can I get back to my functionality where when I start to edit a checked in file that it automatically checks the file out for me?

My VS options for source control are set as follows: (In VS: Tools/Options/Source Control):
Checked-in Item Behavior: On Save = check out automatically, On Edit = check out automatically.

TIA
Noble

[lbauer]

It sounds like you're using the Vault Classic client, is that correct?

Are your files on disk writable or read-only? Does the attribute correlate at all with the lock that you see in Visual Studio?

If you look in the Vault GUI Client at the status of these files, what do you see?

[Noble Bell]

Yes. I am using the Vault Classic client. Will the other client be better to use?

[lbauer]

The classic client is fine, I just wanted to make sure we were troubleshooting the correct one, as they behave differently.

Are the files for your Visual Studio project on disk writable or read-only?

If you look in the Vault GUI Client at the status of these files, what do you see?

[Noble Bell]

They are writeable on disk.

It does not happen all the time, only on occasion but more frequent than not. When looking at the ones in the past the client was reporting them as still checked in.

It seems to me its behaving like some sort of refresh issue between vault client and ide???

[lbauer]

The Classic Client expects files to be read-only unless they are checked out. If they are writable but not checked out, VS can be confused.

If you are using Classic Client integration, your Concurrent Development Style in the Vault Client->Tools->Options should be VSS mode_Make all files read-only. You might want to checkin or backup any changes to your project, then do a Get Latest with Overwrite to set the Read-only bit on your files.

[Noble Bell]

Ok. I have done as you suggested. I will let you know if it occurs again. Thank you for your time and help.

[lbauer]

Ok, let us know if you run into this again.