Vault 4.0.5 introduces the Change Vault Bindings dialog for binding projects, unbinding projects, and correcting binding errors. If you are binding multiple projects, or a solution which contains multiple projects, you will be asked to map a working folder for the Deepest Common Ancestor of all of those projects. In the simplest case, suppose that you are mapping two projects in an unbound solution. If the working folder is structured as:
C:\work\Project1
C:\work\Project2
then, you will be asked to provide a working folder mapping for the C:\work directory on your disk.
If you have a slightly more complicated example of two projects structured as:
C:\work\Project1
C:\work\otherfolder\Project2
You will be asked to provide a working folder mapping for the C:\work directory on your disk.
The most common case in which the Deepest Common ancestor is completely unexpected is when the two projects being mapped share no common ancestor other than the root of the drive. For example:
C:\inetpub\wwwroot\TestWebSite
C:\work\Project2
The Deepest Common Ancestor would be C:\. If this is the case, it is advisable to bind each project one at a time.
What is the Deepest Common Ancestor?
Moderator: SourceGear