Visual Studio 2005 / Vault 3.5.2.5087 / Exclusive Locks

joshdrew · Post by **joshdrew** » Tue May 29, 2007 11:07 am

I keep getting the following error within the VS 2005 Environment:

I followed the directions and set the repository option to NOT have exlusive locks

Then went into both visual studio environments under tools -> options -> source control -> plug in settings -> advanced and uncheck exclusive locks.

I restarted both environments and still get this error. If I check out the project file with user 1 and then try to "add" a new file with user 2, it needs that project file checked out and cannot perform that action.

Any thoughts?

Beth · Post by **Beth** » Tue May 29, 2007 2:37 pm

Was this project previously controlled by VSS?

joshdrew · Post by **joshdrew** » Wed May 30, 2007 7:16 am

No. Brand new project.

I was sure I selected SourceGear as my Source Control Provider. Then I chose "new project" and placed the project on my c:\PROJECTS folder. Then I clicked "add solution to souce control" and followed the source gear prompts. Seems like all is well except 2 people cannot check out or add files.

Beth · Post by **Beth** » Wed May 30, 2007 9:48 am

I'm not sure if the file you are opening is a binary file or not. I will mention though that binary files can only be exclusively checked out since they are not mergeable.

The file looks like a source control file of some sort that I'm not familiar with (looking at .vspscc). Try adding that to the mergeable files list?

I'm not sure though that making that a mergeable file would be the best idea, but if one wants to not have exclusive check-outs, the files would need to be mergeable. With .proj and .sln files, the merging of those files can often break the project, so it's not recommended with any source control product.

joshdrew · Post by **joshdrew** » Thu May 31, 2007 3:09 pm

Nope, it is not a binary. It is an xml. It the the primary container file for all .NET solutions

Beth · Post by **Beth** » Fri Jun 01, 2007 7:27 am

Did you add it to the mergeable files list? You may need to restart IIS after doing that. Just open a command prompt and type iisreset.

joshdrew · Post by **joshdrew** » Fri Jun 22, 2007 10:29 am

I'm back. The problem is we need the .cspoj file to have the ability to be checked out by multiple people since that is the 'container' file for the .net web projects. That file should be able to be merged with out a problem.

I restart the service, IIS, machine and still no luck. Still says exclusive locks are on when they are not.

Beth · Post by **Beth** » Fri Jun 22, 2007 2:58 pm

In order for Vault to allow items to not be checked out exclusively, you need to add them to the mergeable files list. Add *.csproj and *.csproj.vssscc to your mergeable files list.

I know you have a reason you want to do this, but just so you know, VS generally doesn't play well with those files being able to be merged.