Skip to main content
A
AIR-Chayah
Inspiring
February 26, 2013
Question

Branching does not work with RH9, TFS, & Microsoft Visual Source Control

  • February 26, 2013
  • 1 reply
  • 1920 views

Our release engineer, who is experienced with TFS and Source Control, has not been able to successfully branch the Release 1 project to a Release 1.5 branch in source control.

After some experimenting, he found that the XPJ file is not being updated with the correct path. He edited the path to the new path, but finds that there is still something in RH that is holding on to the original path.

Does anyone know whether this is a known problem and whether Adobe RoboHelp plans to fix branching in a future release? (Or is it fixed in RoboHelp 10?)

Thank you.


Carol

This topic has been closed for replies.

1 reply

Captiv8r
Captiv8r
Legend
February 26, 2013

Hi Carol

I know that the XPJ file parallels what is also in the .CPD. Wondering if deleting the .CPD would make a difference?

Cheers... Rick

A
AIR-ChayahAuthor
Inspiring
February 27, 2013

Dear Rick, William, and everyone else.

Yes, deleting the CPD did work. And here's how our release engineer managed to branch Version 1 to Version 2. Our [SourceBranch] was "Main" (for Version 1) and our [TargetBranch] was "R2_Main" (for Version 2).

  1. Branch from [SourceBranch] to target [TargetBranch].
  2. Map, and then ‘Get Latest Version’ of the [TargetBranch].
  3. Locate the .CPD file within the newly created [TargetBranch] in ‘Team Explorer’.
    • Perform a Delete operation on the .CPD file/
    • Check in the pending change.
  4. Locate the .XPJ file within the newly created [TargetBranch] in ‘Team Explorer’.
    • Check out the .XPJ file.
    • Open the .XPJ file in a text editor (Notepad, Notepad++, EditPlus etc…).
      • Modify the path to Team Foundation Server (TFS) that points to the old [SourceBranch].
      • that is: modify $/Help/[SourceBranch]/…/…/…to point to the [TargetBranch].
    • Save the file.
    • Check in the .XPJ file .
  5. Open the .XPJ file in RoboHelp.
    • RoboHelp should create the .CPD file automatically, but not check it in.
  6. In ‘Team Explorer’, browse to the directory where the .CPD file used to exist.
    1. Click ‘Add File to Source Control’.
    2. Select the .CPD file.
    3. Check it in.

Everything appears to work correctly.


Carol

Willam van Weelden
Willam van Weelden
Inspiring
February 27, 2013

Hi,

You should not add the cpd to source control. You can set RoboHelp to rebuild the CPD on opening. The CPD is just a cache file to allow faster project editing.

Greet,

Willam

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices