Project node count mismatch

matlaf · Post by **matlaf** » Thu Oct 18, 2007 7:54 pm

Hi,

I'm new user of Vault. I test VSS import utility and import on of our database to a repository.

When I unbinded and tryed to bind my solution to Vault I've got Project node count mismatch.

I read some thread on the forum and one seem to say that source vault doesn't support a solution where two project are contained in one same folder. I our solution we have this situation.

Solution folder
Solution 1
Projects folder
- Project1.vbproj
  Project2.vbproj
  Project1 sub folder
  Project2 sub folder

We use V 4.0.4.15848.

We need this feature because we have more than 30 projects in this situation. Also this situation is caused by a third party. It will be difficult to change the folder structure in it.

If vault support two project in the same folder what else can cause this problem?

Thanks,

lbauer · Post by **lbauer** » Fri Oct 19, 2007 7:37 am

This has been fixed in Vault 4.0.5. You can download the Beta here:

http://www.sourcegear.com/vault/downloads.html

matlaf · Post by **matlaf** » Fri Oct 19, 2007 8:03 am

Do you consider this beta as stable version?

Is it a possibility of corruption if we use it in production environment?

When the real version will goes out, will it be a simple upgrade from the beta?

Thanks,

lbauer · Post by **lbauer** » Fri Oct 19, 2007 10:30 am

It's fairly stable, but it is a Beta.

Since this an IDE integration issue, you could just install the Fortress Client Beta 4.0.5, which wouldn't cause any server-side issues or data corruption.

When the final release is out, you would uninstall the Fortress Client Beta and install the new release.