Solutions, projects and repository tree structure

rshillington · Post by **rshillington** » Thu Jul 26, 2007 9:25 am

It seems that if the sln file in the repository is not above project file in the repository VS / Vault is unable to load the project when opening the solution from Vault. Is that a know bug? Is there a workaround?

Regards,
Ralph Shillington
(vault 4.0.2 using the 2005 integration piece)

lbauer · Post by **lbauer** » Thu Jul 26, 2007 10:01 am

This is a known issue when opening from source control. The workaround would be to put project files below the solution, or another option would be to use the VS 2003 integration (MSSCCII) with VSS 2005 until this structure is supported.

gmagana · Post by **gmagana** » Thu Jul 26, 2007 12:34 pm

I've gotten this to work with the 2005 provider (Fortress/Vault 4.02 version), but I've had to do some wierd steps. This is only a problem when you "Open From Fortress/Vault" for the first time. Once your projects are on the working directory there are no further problems.

Here are the steps I followed for my non-trivial solutions:

- When you open the solution from the Vault/Fortress server, you will get the projects outside of the solution tree as "unavailable." This is ok. If you check the working directories for the missing projects, nothing at all is there.

- Close VS (I think it requires a close of VS rather than just a close solution).

- You have to get the missing projects by hand using the Vault/Fortress client. Do a get latest on them.

- Re-open VS and load the solution from the working folder. Now everything should be OK.

Hope this works for you.