You can always add the files in CVS and manually check in and out before opening the RoboHelp project. But that is probably not what you are looking for. To allow RoboHelp to work with CVS natively, you will have to install an MSSCCI plugin for CVS. Once that is set up, you can add the source control through RoboHelp.
I can't help you with your plugin question, but for the manual process, when you add the project to source control, do not add the following files: xpj, cpd, ldb. These wouldn't be added if you used Robohelp to add the project to source control and cause problems because they contain user/machine specific infrormation.
For daily work:
1. Check out all files.
2. Open Robohelp and work on the desired files.
3. Close Robohelp
4. Check in all files. You may need to manually add or delete files as appropriate at this point too (and remember not to accidentally add the xpj, cpd or ldb).
A quick question. If I do not check-in the xpj, cpd, and ldb files, will it still be OK for peers who are working on the same project? I mean, if I do not check-in these files, peers will not get updates that may be happening in these files.
xpj should definitely be checked in to source control.
The files to exclude from source control are .cpd, .ldb, .pss.
There are no problems with peers not getting updates to these files - in fact, getting the updates causes big problems. As I said, if you used Robohelp and Robo Source Control, those files will not be added in to version control at all.
Some people recommend this file is not checked in, but I have not had any problems checking it in, and have found it a useful backup a couple of times.
10
Replies
AdChoices