Connect to branche

[RobWestland]

Hi,

In uniPaaS I connect to Vault with the following 2 lines. They are part of a larger file, but these 2 lines are relevant.
<VCProjectName val="$/trunk/Projects/lo"/>
<VCProjPath val="http://versioncontrol/VaultService|EuroPort:4"/>

My project is saved in $/trunk/Projects/lo

After I made a new branche, it is stored in: $/branches/V1.0/Projects/lo

Then I do a "Get latest version" of V1.0

Of course is the above mentioned file in the trunk the same as in the branche.
When I do a chechout of a file in the branche (with uniPaaS, not with the Vault-client). I can see in the Vault-client that the file in the trunk is checked-out and not the one in the branche.

When I do the same with subversion, the branche on my local disk is connected to the branche on te server and the trunk on my disk with trunk on the server.
With Vault is seams that the 2 versions on my local disk both connect to trunk on the server.

Best regards,
Rob

[lbauer]

We haven't tested Vault with uniPaaS, so we're not familiar with how it works with Vault. However, what you're describing sounds like a known issue with Visual Studio and Classic Client integration.

When projects or solutions are bound to source control, binding information is written in the files or points to information in other source control files. Binding are associations between working folders and projects in source control.

Branching doesn't modify that information, so if you have a branched solution open and checkout a file, the file in the trunk might be checked out.

In Visual Studio, users unbind their solutions/projects and rebind to the proper location in the Vault tree. Can you do something like that in uniPaas?

Here's a Visual Studio example:

http://support.sourcegear.com/viewtopic.php?f=13&t=194

[RobWestland]

I can not unbound/bound my application to a specific location.
The only reference to the server is:
<VCProjectName val="$/trunk/Projects/ab"/>
<VCProjPath val="http://versioncontrol/VaultService|EuroPort:4"/>

But in subversion it is:
<VCProjectName val="ab"/>
<VCProjPath val="http://versioncontrol.syntel.nl:83/svn/ ... 0|rev:HEAD"/>

In subversion it works the way I want.
I think that the subversion-client ignores the information about the path. Because in subversion in each working dir you have an hidden folder named ".svn" and in that folder is a file called "entries". When I look in that file, I see a reference to the trunk or to the branche. So subversion knows where to connect to.

When I have 2 folders in Vault (trunk and branches) I can't see any reference to the location.

In short:
In subversion has each folder it's own bounding to the location on the server and in Vault that bounding is somewhere else or doesn't exist.

[lbauer]

Most SCC compliant development environments integrate with Microsoft's MSSCCI api. That's what Vault uses for Classic Client integration.

This integration creates a mssccprj.scc file, which contains binding information. For example:

Code: Select all

SCC = This is a source code control file

[Project1.vbp]
SCC_Aux_Path = http://myvaultserver/VaultService|:12
SCC_Project_Name = $/VisualBasic/Project2

Look for an mssccprj.scc file in your project directory on disk.

You might be able to manually edit this to point to right path.