Unexpected behavior when trying to re-add a solution

Nihimon · Post by **Nihimon** » Fri Sep 14, 2007 8:57 am

I'm in the process of adding all of our existing solutions to Vault as part of a migration from VSS 6.0d. In doing so, I mistakenly added a Solution in the wrong project folder. I deleted this from Vault, Unbound the Solution, and tried to re-add to the correct folder, but Vault put it back in the original folder where I had mistakenly put it.

Eventually, I found that I had to Move the Solution in Vault, then Get Latest Version from Vault (when I tried to Open From Vault from VS none of the projects loaded.)

I've found a work-around, but wanted to ask if this is expected behavior.

Thanks,
Matt Knowles

Beth · Post by **Beth** » Fri Sep 14, 2007 10:55 am

It shouldn't but more information is needed so I can see what's going on.

What version of Vault are you using?

What setting do you have in VS under Tools - Options - Source Code Control? (By that I mean if it's VS 2003 compatible client or VS 2005 client or something else.)

What kind of project is it?

ian_sg · Post by **ian_sg** » Fri Sep 14, 2007 11:01 am

This happened because the working folder assignment(s) from the first time you added the solution were still around. 4.0.5 checks for this and forces you to remove conflicting working folder assignments before performing the add. In the mean time, you have to check for and remove those old working folder assignments yourself.

Nihimon · Post by **Nihimon** » Fri Sep 14, 2007 11:39 am

Thanks for the reply.

I must say I'm very pleased with the level of support I've received in these forums. And I'm happy to adjust to any quirks peculiar to Vault. I well remember the learning curve associated with VSS and figuring out how it wanted me to use it... (Solution.root, gah!)