Vault Visual Studio Enhanced Client

[Frank.Neumann]

So far we have used the classic client for source control integration.
Today I tried out the msscci2vsip.exe power tool for an easy migration from the classic to the enhanced client.
This way I found out that this tool will change the solution and project files look the following way:
Solutions:
Classic:
GlobalSection(SourceCodeControl) = preSolution
SccNumberOfProjects = 24
SccLocalPath0 = .
CanCheckoutShared = true
SccProjectUniqueName1 = ..\\..\\src\\Pace\\EWB\\Framework\\ApplicationAbstractionLayer\\ApplicationAbstractionLayer.csproj
SccProjectName1 = $/Products/EngineeringWorkbench/trunk/src/Pace/EWB/Framework/ApplicationAbstractionLayer
SccLocalPath1 = ..\\..\\src\\Pace\\EWB\\Framework\\ApplicationAbstractionLayer

Enhanced:
GlobalSection(VaultVsipSolution-v1) = preSolution
VaultHost = http://vault.pace.de/VaultService
VaultRepositoryID = 18
VaultRepositoryGUID = 28032ED2-74DC-4199-9BA0-BCEB1882A33B
ProjectCount = 23
ProjectRelativeDiskPath1 = ..\..\src\Pace\EWB\Framework\ApplicationAbstractionLayer\ApplicationAbstractionLayer.csproj

Projects:
Classic:
<SccProjectName>SAK</SccProjectName>
<SccLocalPath>SAK</SccLocalPath>
<SccAuxPath>SAK</SccAuxPath>
<SccProvider>SAK</SccProvider>

Enhanced:
<SccProjectName>ApplicationAbstractionLayer</SccProjectName>
<SccLocalPath>18~28032ED2-74DC-4199-9BA0-BCEB1882A33B</SccLocalPath>
<SccAuxPath>http://vault.pace.de/VaultService</SccAuxPath>
<SccProvider>SourceGear Vault Visual Studio 2005 Client:{7BE9CE03-56BF-4682-9C06-78C68B134B30}</SccProvider>

I was surprised by the changes applied to the project files: Our previous settings to get the source control information from the solution file were replaced with specific settings.
The consequence for us is, that for branch scenarios all project files have to adapted in an unknown way in order to keep the binding information up to date.
Using the classic integration we had only to adapt the repository settings in a few solution files.

Please provide me with an idea how branch scenarios are supported using the enhanced client:
1. How can I branch from the Visual Studio enhanced client in order to keep the binding information up to date?
2. How can I manually adapt the binding information for the Visual Studio enhanced client when I create a new branch in the Vault GUI client?

Thanks for your help!

Frank

[jeremy_sg]

Hi Frank,

In the Enhanced client, you should not need to change repository path when you branch. The Enhanced client examines the working folder path that is set to map the project to a repository path. In the project files, we only store the information to find the server and the repository. From there, we use working folder mappings to determine the repository location of the project file you're opening.

[Frank.Neumann]

Hi Jeremy,

thanks for the clarification.

FRank