Using Robo Source Control - Saving Project

[Guest]

There are two writers working on one HTML project, both using Source Control Explorer 3.8 with RoboHelp 6. I was the initial creator of the project and added it to Source Control.

When the other writer clicks the "save all" button, it takes 20-30 minutes before the save finishes (when the hour-glass goes away), allowing her to work in the project again.

I have no problems with saving. The Source Control database is on a separate server from either of our machines.

We are new to this work flow so it could very well be something done out of ignorance, but mine works fine and I installed the software on the other machine and helped set it up in Version control.

In Task Manager her CPU usage is maxed out, with the RoboHTML process using about 95 percent. I can see nothing different in her installation/configuration that should cause this. Any suggestions, ideas, would be most appreciated.

[Gravenstein · Accepted solution]

A good place to start would be to have your colleague rebuild her cpd file. (In this order: make a backup copy of the project, check in all files, close the project, delete the cpd file, and then open the project again.)

RoboHelp will rebuild the cpd file when she opens the project. Depending on the size of the project, it can go quickly (almost unnoticeable) to REALLY slow (hours). Just let it run for as long as it needs to this time--subsequent instances of opening the project should be normal.

HTH,
G

[Guest]

G,

Thanks for the information. I know you said "her cpd file," but just to clarify so I don't make a fatal error, is that the cpd file on her machine, or the cpd file in the project folder on RoboSource Explorer, under version control?

Regards,

Joe

[Gravenstein]

Uh, oh. The cpd file should not be in source control. If it is, then you have a problem. Just to be sure, I'm referring to the projectname.cpd file. If it's really in source control, that's a sign that the project was added to source control incorrectly. The project should always be initially uploaded to source control via the RoboHELP app, not via RoboSource Control Explorer. This is a huge user trap that (nearly) everyone falls into at least once. This might also account for your colleague's problems.

G

[Guest]

G,

I was mistaken. The cpd file was not in source control. And the process you suggested seems to have done the job. Thanks very much. I'm posting a new question regarding another facet of source control.

[Guest]

HI Gravenstein,

Are you saying that a project should not be loaded into RoboSource Control through RoboSource Control? The documentation in RSC makes no mention of this. As a matter of fact, when I do a search in the RSC help, there isn't a mention of RoboHTML or RoboHelp. So all of my projects were loaded through RoboSource Control as instructed by the RSC documentation. Do I have to reload it? Looks like it cause I see the cpd file in RSC. Bummer.

[Gravenstein]

Sorry, HockeyTime, but that is indeed the case, at least up through RH6. I think RH7 is the same, but I don't know for sure. When you load via RSC, ALL the project files get uploaded into the DB, which causes frequent and peculiar problems. If you do the upload via RH, only the appropriate files get loaded. It is poorly documented and not intuitive, but it is the way it is. It might be simplest to create a fresh, new DB and start over.


G

[happileigh]

Hi Gravenstein,

Do you know if your advice about loading a project through RoboHelp (and not through RoboSource Control) applies to RoboHelp for Word projects as well? Thanks for your help!

[Gravenstein]

Hi, happileigh, and welcome to the board!

Sorry, I don't have any experience using RoboHelp for Word with RSC. I took a look at the RH for Word help, and it implied that there wouldn't be a problem. Mind you, the help also did not mention RSC by name, so it must have been written before there *was* a RoboSource Control.

If you're not experiencing any problems, you're probably OK.

G