This content has been marked as final. Show 4 replies
As MergeThis pointed out, you are talking about output files here. So I'm afraid that there is no way past that. However, I'm also aware that sometimes folks want to use Source Control as a mechanism for the installer to grab the files needed for the build. So I can see where you may have a need to store them there. If this is the case, I may have a solution to offer.
Use the built in publisher! Just define a different folder where your Subversion files are stored. Then when you Publish your output files from the WebHelp output folder to the other one, the Subversion files won't be deleted. All that will happen is that RoboHelp will dutifully replace the files that should be replaced.
Just a thought... Rick
If you try Rick's suggestion, can you post back and let us know how it goes? I have had the same problem with Subversion and have been using that copy/paste workaround. Thanks,
We do use source control to make doc files available to the installer for the build.
Rick's publish-to-the-check-in-folder suggestion worked! Thank you!!
(For the record, RH was deleting *some* files from the Subversion subfolders, not just deleting *all* the non-RH files in the WebHelp output subfolders.)