My institution is going through a conversion of our core systems in September of this year and I need to develop a process for updating the 700 helpfiles I have within my helpsystem. Is there a way to create a mirror image of my helpsystem so that I can work con-currently on both helpsystems? This way when it comes time for conversion in September, I can simply publish the mirror image copy that has been updated with the correct procedures and the old version would no longer be live.

I am currently using RH7 but we are in the process of being updated to RH9 but I am not there yet. Any ideas or suggestions would be greatly appreciated.

Thanks again for the information! Forgive me, but I don't understand how copying my project files to another location would allow me to have two seperate versions that I can work on within Robohelp? I want to be able to work on both the mirror image copy and the current "old" version in Robohelp, so on September 1st, I can publish the mirrored "new" version I have prepped for the conversion and it will be live on the servers for the employees to use immediately. Does this make sense?

Actually what I want is to have two seperate projects that have the exact same helpsystem information in it. The project I am referring to in this string is called "ccc help files". So what I want is to have another project called "ccc help files mirror". Then I can work on the ccc help files mirror project over the next few months and it will not interfere with the ccc help files project. Then come September 1st, I would delete the ccc help files project and publish in its place the ccc help files mirror project.

Does that make sense? So they don't have to share anything, they need to be two free standing projects independent of each other but they have the same information in them. Is this possible?

I think we are all struggling here because what you say you want in the above post in this thread (post number 6) is what was covered in the first reply.

If you create a copy of your existing project in Windows Explorer, you will have Project 1 (the existing project) and Project 2 (the copy of Project 1 as it stands now. Call them ccc help original and ccc help mirror if it helps.

At the time you copy the project, it will be an exact copy. You will then work on the mirror copy and what you do there will have no impact on the original and you can trash the original on September 1.

I hope you guys aren't talking at cross-purposes - when Colum & Peter talk about "project" they mean the RH project; a collection of files and folders that you use to create your help from. You sound like the "project" is the actual help output itself. With the former interpretation, you would just start RH up, and browse to the new copied project's location and grab the project_name.xpj file. You'd then manipulate the content inside RH, and generate new help output at the end of the process. With the latter, this idea of copying the help and then manipulating it would be all manual using some HTML editor like Dreamweaver to edit the pages.

Thanks for the response! I think what I failed to mention since I have never been on this forum before is that, I pull my helpfiles from a database using Robosource Control. So even if I copy my project to a new location and click on the xpj file from that new location, when I update a file in the project it gets saved back to Robosource Control, so when I go back to the current project the changes I made in the copied project will still show in both projects.

So what I need to figure out is how to mirror the ccc helpfile project in Robosource Control so that I can pull the mirror project into Robohelp and make my changes and then publish it when the conversion takes place. Any ideas on how to do that?

Personally, I dislike just double-clicking the XPJ to open things up. It may work fine on your system and if it does, I'd say go for it. But I'm notorious for installing many different versions of RoboHelp and other apps on the same system. So I have avoided working that way to open projects because I want to easily control what version of RoboHelp opens when I open a project. My way of working involves first opening RoboHelp (the version I want to use for the session) then opening the project.

Can't help you there with adding the project back to source control. I'm aware of Source Control. I know how it's supposed to work in theory. But I've never used it with RoboHelp. At least not in the recent methods where it's all integrated and RoboHelp operates on your behalf by checking things in and out and all that rot. Personally, I've always avoided integrating because it adds a new level of complexity to the mix. This thread is an excellent example of just one of the many reasons.

Certainly I think I'd try by reversing the steps. And as with anything where you are modifying files, I cannot stress this enough. backups Backups BACKUPS!!!!!