Copy link to clipboard
Copied
Hi,
I'm using Adobe Robohelp 9 with Team Foundation Server 2012 on Windows 7 - 64 bit. I've also installed Microsoft Visual Studio Team Foundation Server 2012 MSSCCI Provider. I've mapped all the project folders on my machine. We create HTML help (.chm) for our application.
I have different versions for each module of our entire product on Team Foundation Server 2012 (As we have multiple modules in our product), for example x+1, x+2, x+3 and so on.
Each module has different Robohelp projects for every version/branch. This means, if the Online help for any module from any version is changed, we update it in the respective version of the Online help project.
When we move on to the next version, due to binary files, the next version contains the same path and properties of previous version. We need to have different project for single module for the next version. For this, I have changed the TFS project path of every .xpj project for every version. For example, if I'm working on version x+2, then I've changed the TFS project path from x+1 to x+2 manually on x+2 version/branch and then started working on it.
As these Robohelp projects (for each module) are mapped to my local folder on C drive, it shows a single workspace mapped with same path on my machine. This should be the ideal condition for my all projects as follows:
But sometimes when I try to update any file from version x+2 and then check-in my changes, the changes are getting checked-in to the previous version, i.e. x+1. And if I see the workspace of the x+1 version, it shows one more wrong workspace added below the correct one. This new workspace contains the Source control folder path of x+1 version and the Local folder path of x+2 version. That means, my robohelp project folder of x+2 version from my local drive is getting mapped to TFS folder of version x+1. That is why all the changes done in Robohelp project files from x+2 version are going in to x+1 version.
The strange here is when I try to check-in my changes in x+2, it shows the correct path of x+2 version. But they all go to x+1 version, which should not happen.
If anyone can help me in this problem, it would be a great help!
Thanks in advance and waiting for solution,
Dipali
Copy link to clipboard
Copied
So, if I understand correctly, you create a duplicate of the project and
check that in on a different location in TFS. That is the way to go.
My guess is that the XPJ still references the old version's path. Try
checking out the XPJ with TFS and open in with notepad. Search for
'vc::cookie'. Check that the path there points to the correct path of
the project in TFS. It probably still references the old path and so
RoboHelp will check it in at the old path.
Kind regards,
Willam
Copy link to clipboard
Copied
Thanks Willam,
But I have already changed the project path in TFS in xml/notepad and checked-in the same. There were no references of the previous version. Still there is a problem.
Copy link to clipboard
Copied
Hmm. That's how I moved some project between locations.
Did you remove the CPD file before opening? The CPD file also holds a
reference to TFS.
Are you using any kind of branching or the like for multiple versions?
I'm not sure how RH plays with branches.
Kind regards,
Willam
Copy link to clipboard
Copied
Hi,
Yes mostly I remove the .cpd file but I might missed it once in a while. Is that a main reason? Deleting CPD is compulsary?
If it has to be deleted everytime, then I'll do that. But how that new wrong workspace got added and maaping changed, as written in my first write up (discussion)? Is it due to CPD file?
Thanks,
Dipali
Copy link to clipboard
Copied
Deleting is compulsory if you move the TFS path. It is a database of all
settings and it also holds the location of the help in TFS. My guess
would be that this causes your problem.
You can set RoboHelp to automatically recreate the CPD when the project
opens. It's an option in the settings.
Kind regards,
Willam
Copy link to clipboard
Copied
Hi Willam,
Thanks a lot for the "One click" solution on this CPD file problem!
Regards,
Dipali