Multiple Projects in VS2003

tomt84 · Post by **tomt84** » Fri Jun 23, 2006 3:17 am

dan wrote:Is your local user option "Always Request exclusive locks" turned off (in Tools->Options->General)?

yes.

2) .csproj is mergable for this repository.

3) "Always request exclusive locks" was checked. oops.

4) Now it's checked out but not exclusively.

I'll go do this now on our other dev's machine and see if this fixes it - I suspect it will. My bad.

tomt84 · Post by **tomt84** » Fri Jun 23, 2006 5:53 am

Hokay.

The exclusive checkout issue has gone, but now VS / Vault thinks that .csproj files are mergeable, it does so. Which causes really dodgy build behaviour - on build VS complains about some files being mentioned twice in the .csproj file. If you manually view it, it's not wrong. Parts of the file do seem to have been duplicated.

I've taken .csproj off the mergable list.

dan · Post by **dan** » Fri Jun 23, 2006 9:18 am

Ironically, that is why .csproj files are not in the mergable file list by default

tomt84 · Post by **tomt84** » Tue Jul 11, 2006 8:46 am

Solution for this seems to be to coordinate changes to the csproj file between developers. Tell everyone you want to move/rename/delete a file, do your changes (checking first that you have got the .csproj file exclusively), then check in your pending changes. Then get everyone else to do a "Get latest recursive" on the project to replicate the changes to the .csproj file to their local copy.

Also it seems to be more reliable to rename files from within Vault itself.

Sound reasonable?

Post by **jclausius** » Tue Jul 11, 2006 8:52 am

Yes. That kind of protocol should definitely help.