Skip to main content
June 5, 2008
Answered

What is included when generating with version control on?

  • June 5, 2008
  • 2 replies
  • 508 views
When using source control, is it possible to generate a single source layout for an "old version"? E.g. I have written documentation for a version of our product that is to be released in a few days, but I don't want to generate it yet in case of last minute changes. In the meantime I would like to continue working on things for the next version. Is that possible? Or will everything I up to the time I generate be included?
I'm using RH5 at the moment, but can upgrade if necessary.
This topic has been closed for replies.
Correct answer Gravenstein
Hi fonnes -

RoboHelp will generate output from the files that are resident on your pc at that moment. At the time of generation, RH does not check whether the files are current or not; that happens when you open the project, not when you generate.

From where you sit right now, I would be wary of continued development that you don't want included in your immediate release. I would consider two options for dealing with this:
1. Add your new material, but apply build tags to it so that it is excluded from your build. You can remove the build tags later.
2. Alternatively, clone the project source files that are on your pc now. Keep one copy in a safe place as an archive copy for your release. (This is probably a good idea in any case.) Place another copy in a new directory, and remove it from source control as follows:
a. Delete the following files from the root level of the project: pblsvrs.sss, mssccprj.scc, projectname.cpd, projectname.pss.
b. Using Notepad, open projectname.xpj.
c. Delete all entries between <miscproperties> and </miscproperties>, but leave both tags.
d. Close Notepad, and save the xpj file.
You now have a project that is removed from source control. You can make any final changes before your release in this version of the project and generate from here. (Note that those changes would also have to be added to your "real" source-controlled project as well.) In parallel, you can continue with new development in your source-controlled project.

Theoretically, you should be able to label different versions of your project in RSC. However, at this late stage of the project, I doubt that you want to experiment with that. I'd go with one of the two options above.

I'd definitely encourage you to store that archived copy of your project for any milestone release, just for your own protection from the dreadful influence of Murphy's Law.

HTH,
G.

2 replies

June 10, 2008
hi Gravenstein
I had also considered using build tags, but was hoping maybe there was a simpler way. I think I'll just go with the tags this time, since I know how to do that, and look into your other suggestion later.
Thanks for your help.
Gravenstein
GravensteinCorrect answer
Inspiring
June 5, 2008
Hi fonnes -

RoboHelp will generate output from the files that are resident on your pc at that moment. At the time of generation, RH does not check whether the files are current or not; that happens when you open the project, not when you generate.

From where you sit right now, I would be wary of continued development that you don't want included in your immediate release. I would consider two options for dealing with this:
1. Add your new material, but apply build tags to it so that it is excluded from your build. You can remove the build tags later.
2. Alternatively, clone the project source files that are on your pc now. Keep one copy in a safe place as an archive copy for your release. (This is probably a good idea in any case.) Place another copy in a new directory, and remove it from source control as follows:
a. Delete the following files from the root level of the project: pblsvrs.sss, mssccprj.scc, projectname.cpd, projectname.pss.
b. Using Notepad, open projectname.xpj.
c. Delete all entries between <miscproperties> and </miscproperties>, but leave both tags.
d. Close Notepad, and save the xpj file.
You now have a project that is removed from source control. You can make any final changes before your release in this version of the project and generate from here. (Note that those changes would also have to be added to your "real" source-controlled project as well.) In parallel, you can continue with new development in your source-controlled project.

Theoretically, you should be able to label different versions of your project in RSC. However, at this late stage of the project, I doubt that you want to experiment with that. I'd go with one of the two options above.

I'd definitely encourage you to store that archived copy of your project for any milestone release, just for your own protection from the dreadful influence of Murphy's Law.

HTH,
G.