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 26, 2013

Hi, Rick.

Thanks for the information. Does branching work with RH10? We have one writer using RH10 and will probably migrate everyone in the next couple of months.

I see that RoboColum(n) considers the CPD an “item of wonder”! I’m meeting with the release engineer to try to clean up the problems left by the attempt to branch (unlinked topics, missing topics, etc.) and will suggest that we try deleting the CPD.

Carol

Captiv8r
Captiv8r
Legend
February 26, 2013

Sorry, I don't use source control so cannot comment on whether branching works or not.

LOL on the "item of wonder" bit. There is no wonder to it at all. (Except, perhaps, to wonder why it is still needed in the mix.)

What the .CPD is, is a Microsoft Access database file using a custom file extension. I've since abandoned documenting the innards of it because it is now just a cache file used in conjunction with the .XPJ file and its merry band of other support files.

But it's rife with all sorts of tables that are related to other tables. So my thought was that since RoboHelp seems to be "holding on" to the original path, the .CPD is a likely culprit.

Cheers... Rick

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