Why are .vbproj files checked out exclusive?

neal007 · Post by **neal007** » Wed Apr 23, 2008 8:12 am

We have a team of devs and all of our solutions are unique to each dev and the references each project uses to reference other projects in the solution are "project" type references. All works fine. The problem though is that on some projects the .vbproj file is always checked out exclusive. We do not have the request exclusive locks checked in the vault advanced options. How can we prevent these from being exclusively checked out? If another developer has it checked out exclusive then I can't add files or folders because of the .vbproj file becoming uneditable while exclusive to another dev.

ian_sg · Post by **ian_sg** » Wed Apr 23, 2008 8:41 am

See the FAQ: http://support.sourcegear.com/viewtopic ... 9672#39062

neal007 · Post by **neal007** » Wed Apr 23, 2008 8:54 am

Good grief! You filed for an ISBN for that yet??

I'll try adding the .vbproj files to mergeable types and see if that helps us out. Hopefully there are no "I wouldn't do that's" from you!

ian_sg · Post by **ian_sg** » Wed Apr 23, 2008 11:27 am

As long as you're cautious if a merge is necessary, taking into account the caveat from the FAQ, you're fine:

So why aren't project or solution files in the mergeable list by default?

These files are machine generated, and there are no guarantees that two different instances of Visual Studio are going to produce the same file based on the same changes. (it sometimes orders things differently, for example.) In practice, this means that you need to review the results of any auto-merges (which happen during Get Latest if that option is selected) or always perform these merges manually (via the Show Merge command).

We work this way and I can't recall it ever causing us any trouble. You're also implicitly working this way if you work in CVS mode and don't use IDE integration.