Skip to main content
June 10, 2008
Answered

Using Robo Source Control - Saving Project

  • June 10, 2008
  • 1 reply
  • 1116 views
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.
This topic has been closed for replies.
Correct answer Gravenstein
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

1 reply

Gravenstein
GravensteinCorrect answer
Inspiring
June 10, 2008
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
June 11, 2008
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
Inspiring
June 11, 2008
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