csproj file and guids (or VSS references)

George Mills · Post by **George Mills** » Tue Aug 24, 2004 3:34 pm

How does Vault handle .vcproj files with respect to all the VSS meta data crap in them when they are branched.

We have had fairly complex problems when branching projects and keep VSS integration working. We had to create a solution file for each combination of branched projects. And basically has to remove and add the projects again in the solution file that uses the branched project.

This is because the .vcproj files contain pointers directly into the VSS archive.

Can anyone comment on how they deal with issues like this and how Vault handles them. It was a nightmare.

dan · Post by **dan** » Tue Aug 24, 2004 4:35 pm

Vault works the same way VSS does in this regard, because the culprit is the Visual Studio IDE keeps binding info to the old folder in SCC, not the new one.

MS has an article on it at http://support.microsoft.com/default.as ... -us;317925 Hopefully, it will be addressed in the next version of Visual Studio.

George Mills · Post by **George Mills** » Tue Aug 24, 2004 7:58 pm

The article says it's fix in Visual Studio .Net 2003. I'm not sure if that is the same problem, but it definitely smells like it's in that area. We are running VS .Net 2003.