Robohelp projects are only automatically updated when you use Robohelp to add/remove files. The 'easiest' solution is to get a Robohelp license for each user who needs to update this project and only make changes through Robohelp. However, this might not be possible in your organisation.
Getting the latest files from source control and deleting the .cpd file before you open the project might update some of the information, but I'm unsure how much would be detected.
You can set up RH8 to automatically delete the cpd file every time, so you don't have to remember to do it manual. Just note that when you do this, depending on the size of your project, it can take quite a while. I think it's in Tools > Options somewhere, but I don't have a copy I can look at, at the moment.
Try that, and see how you go.
Thanks for the reply!
I was able to get this to work by doing the following.
- Tools > Options > General Tab > Check "Clear project cache (.cpd file) before opening any project"
- Delete ProjectName.cpd from SourceSafe
- Remove read only flag from ProjectName.cpd in my working directory
When I opened the RoboHelp project it was automatically updated to reflect the changes that the other developer had made to the HTM file.
Thanks again -
The following project files should also not be added to source control:
.ldb (not always produced)
I disagree about the hhp file, but definitely the others and the cpd should not be source-controlled. Glad you got it sorted out.
Surely this is not just a matter of opnion?
The files are either machine-specific or chm-specific, and should not be added to source control.
This "opinion" is shared by Adobe, which chooses to exclude these files when you add a project to source control from the RoboHelp app.
I haven't seen any difference in the hhp file between the different chm files we generate for a single project. I always thought Blue Sky considered it an 'output' file and thus excluded it from source control like the chm files. (The hhp file is rebuilt by RH on generation if you delete it - don't try this if you are using HTML Help Workshop. )
I consider it a useful backup, in case something happens to the .xpj file.
The HHP is a source file, not a backup file. It's the primary control file used when compiling a CHM file. Unless you specifically add it to baggage, it will not be included inside the CHM when you compile.
Helpful and Handy Links
Yep, I know. Leon and I were disagreeing about whether the file should be excluded from source control or not. I was trying to explain why I like it in source control.
The other reason, which I forgot to post, is in case I need to get the project into a different tool that does not understand the RH xpj. But I think nearly all tools understand that file now, so probably not a big consideration any more, but was when we first added the file to source control many many years ago.
It would also be necessary to source control this file if you were using HTML Help Workshop as otherwise the project would be unusable in that product.