Vault 4.0.2 Project Reference Errors

chuckdesigns · Post by **chuckdesigns** » Fri Aug 17, 2007 11:56 am

We migrated from VSS to Vault 4.0.2, duplicated the exact folder structure, and we are having issues between the solution file and its project references.

When Opening from Vault for the first time and selecting the appropriate solution file within the VS IDE, the solution opens with errors indicating that one or more of the referenced projects have moved and will not be loaded locally.

The relative pathing for project references within the solution file should not need to changed because of our source safe migration b/c the the exact folder structure was set-up in the new Vault repository.

By goiing through the Vault client instead of the VS IDE and getting latest to pull down all solution/project files - then going back into the IDE and refreshing the project connections is successful as a workaround to this issue.

Any isight as to fixing this issue so that the standard "Open From Vault" option within the VS IDE will work?

Beth · Post by **Beth** » Fri Aug 17, 2007 12:44 pm

Were you the first one to open that project after the import? Usually we recommend an unbinding and rebinding for the first person that opens it. The complete instructions when switching between VSS and Vault are here: Importing a solution or project that uses IDE Integration

ian_sg · Post by **ian_sg** » Fri Aug 17, 2007 12:56 pm

There is a known issue where immediately after an open from Vault, some projects don't resolve their references. This only happens immediately following the open from Vault, and can be fixed by closing and re-opening the solution. We already have a fix for this, but it hasn't shipped.

This sounds like the issue you're having. If it's not, if you could send me a 2005 client log and/or a small sample solution that demonstrates the problem, I can investigate further. You can email them to ian at sourcegear dot com.