vbproj files won't update due to read-only locks

neal007 · Post by **neal007** » Fri Nov 02, 2007 5:56 pm

For some reason .vbproj files are not auto-checking out when they are attempting to be edited. When we shared projects among various devs the .vbproj file updates for whatever reason, probably a change in the location on the hard drive of where this project is located or references, etc. We keep getting an error that the vbproj file can't be overwritten and a dialog to save it in a new location (i.e. it's read-only). I have to manually checkout the project to resolve the issue. I'm using the 4.0.5 VSIP client, again, it appears it's not auto-checking out project files.

Beth · Post by **Beth** » Fri Nov 02, 2007 6:35 pm

Is it possible that those files are already checked out by someone? They have to be made mergeable before multiple people can check them out, but merging is bad for that type of file.

neal007 · Post by **neal007** » Fri Nov 02, 2007 6:40 pm

No, they are not checked out. As I mentioned, when this problem occurs I have to right-click, checkout the project and then it's fine. But when I do a Get Latest without first doing a checkout it errors as if it can't update the .vbproj file as it's not checking it out.

Post by **jclausius** » Mon Nov 05, 2007 9:26 am

Neal, can you clarify this some more?

Do you mean you have two sub projects and would like to share files between projects? Or if you could provide the steps to recreate, I'll see if I can find out what is happening.

neal007 · Post by **neal007** » Mon Nov 05, 2007 9:30 am

Jeff,

I have a solution with say 1 exe and 9 class libraries. Another developer opens the solution which updates the .vbproj files due to references, etc. He's done, checks in. I open the solution and see the hourglass symbol meaning my project is out of date, I do a get latest, it fails to update the .vbproj file and gives me an error and then a dialog to save the .vbproj file to another location, a read-only lock situation. I instead do a checkout on the project and the problem goes away. The issue appears that during a get latest it's not checking out the .vbproj file when attempting to edit the file unless I manually check it out first, which obviously also does a get latest if I'm not mistaken.

Post by **jclausius** » Mon Nov 05, 2007 9:49 am

Neal:

Within the Vault GUI client, do you have the Concurrency Option to "Require Check Out before Check In" checked or unchecked?

If this option is not checked, then is it possible this solution was once bound to the VS 2003 Compatible client and the files were retrieved with that client, and then a switch was later made to the VSIP client?

neal007 · Post by **neal007** » Mon Nov 05, 2007 7:40 pm

Jeff,

I'll have to check when I get back from DevConnections, but that setting sounds familiar.

Post by **jclausius** » Tue Nov 06, 2007 9:51 am

No problem.

When you're back, try turning off the read-only file attribute on the files, as that may be where the problem lies.

neal007 · Post by **neal007** » Mon Nov 12, 2007 12:31 am

I'm back Jeff, here is my a screen shot of my Vault GUI options per your question.

Post by **jclausius** » Wed Nov 14, 2007 10:17 am

Neal:

Glad you're back. Hope you had a good time at the conference.

Getting back to your screen shot. It was not what I was expecting.

If the read-only file attribute is OFF for the files in your working folder, does that to solve the problem you are seeing?

neal007 · Post by **neal007** » Wed Nov 14, 2007 10:22 am

Jeff,

I didn't mess with the read-only attribute, instead I did a full checkout of the project to resolve the issue.

Post by **jclausius** » Wed Nov 14, 2007 1:22 pm

Neal, thanks for the info you've provided.

If you do encounter this again, check to see if it is related to the file attributes. That might help shed more light on the problem.

neal007 · Post by **neal007** » Wed Nov 14, 2007 1:24 pm

Correct me if I'm wrong but the files are supposed to be set as READ ONLY on check-in?

Post by **jclausius** » Wed Nov 14, 2007 2:45 pm

In check out-modify-commit , yes.

What I'm wondering if there was an assumption taken in the code somewhere regarding the file's attribute. If the VSIP client exhibits the correct behavior when the read-only attribute is off, then this is a bug.

neal007 · Post by **neal007** » Wed Nov 14, 2007 5:22 pm

Jeff,

The problem just happened again. I was working on my solution and realized I had an hourglass on one of the projects as one of my other devs opened their solution which updated the project refs in the .vbproj file. I checked everything in and then did a get latest and it asked to reload so I said yes to all. Everything looked good. I then went to close the solution and it asked to save the .vbproj file as it obviously updated as my computer has project locations on the D drive and my other dev uses the C drive. It would not allow the .vbproj file to be updated so I had to check it out, save, then check-in. The problem seems to be that when VS.NET updates a .vbproj file with project references it is NOT checking out the .vbproj file.