Project files not being automatically checked out

[Scott Mitchell]

I have been using Vault for about a year now in a two-developer team scenario. In the past it seemed to correctly check out the .vbproj file when I was adding a new file to a project. However, recently I have noticed that it lets me add new files to the project WITHOUT checking out this project file.

The net result is that when my coworker does a Get Latest, he gets the new files but they don't show up in the Solution Explorer since the project file is out of date between my client machine and the Vault server.

I pushed up my versions to the Vault server via the Edit option, but I would like it so that it automatically checks out the project files when I am adding new files to the project. I could have sworn it did this before and am amiss as to why it's no longer behaving as expected.

Any help greatly appreciated! Thanks!

[dan]

I've noticed in the past that if the project/solution file is marked as read-write on the file system, Visual Studio won't check the file out (in some versions of VS), and therefore it doesn't get checked in.

So, verify that the project/solution file is read-only and see if that makes a difference.

[Scott Mitchell]

I've noticed in the past that if the project/solution file is marked as read-write on the file system, Visual Studio won't check the file out (in some versions of VS), and therefore it doesn't get checked in.

So, verify that the project/solution file is read-only and see if that makes a difference.

Yeah, that appears to be the problem. If I make the project file read/write it won't get check out; read-only, and it auto-checks it out.

For the record, I am using Vault 3.0.2 and VS.NET 2003.

I guess this begs the question, "How does my project file get reset to read/write from (previously being) read-only?"

Thanks for your help, Dan.