Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

How do I prevent RoboHelp from adding generated files to source control?

Community Beginner ,
Sep 04, 2014 Sep 04, 2014

I have a RoboHelp 10 project configured to use Team Foundation Server. When my user generates output (e.g. by previewing or 'Generate...') RoboHelp automatically tries to checkout the generated files (add or edit operations). I only want the source files to be added or checked out automatically, not the generated output. It is tying up Team Explorer on the user's computer each time this happens as hundreds of files are reconciled with TFS.

How can I resolve my problem?

BONUS problem I need solving:

So the user has these files checked out because RoboHelp demands it (until my original question is solved). If another user tries to build the same files (like I just did) on another machine, RoboHelp complains that the file is already checked out (regardless if multiple checkout policy is enabled). Then I have to click OK on each file. How to stop this as well and allow multiple users to work on the same project?

529
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Sep 04, 2014 Sep 04, 2014

I solved this issue by cloaking the !SSL! folder. I do not have a solution for the multi-checkout issue however although the cloaking mitigates the huge number of message boxes when generating.

Translate
Community Beginner ,
Sep 04, 2014 Sep 04, 2014

I solved this issue by cloaking the !SSL! folder. I do not have a solution for the multi-checkout issue however although the cloaking mitigates the huge number of message boxes when generating.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Sep 04, 2014 Sep 04, 2014

Alternatively, you can generate to a different folder than the !SSL! folder. If you, for example, select C:\Help-output, you won't run into this issue either.

Though it's strange that you even have this issue. Did you check in the !SSL! folder in source control at some point?

Kind regards,

Willam

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 04, 2014 Sep 04, 2014
LATEST

I did originally check in the !SSL! folder when I added the original project to source control. TFS 2010 typically doesn't check files out on its own like that though. If I open a file in notepad and then save it TFS doesn't know about it. This behavior is different in later versions.

As I said, cloaking this folder solved my original issue for me. I don't need the generated outputs to be in source because I have TFS building it on demand.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
RoboHelp Documentation
Download Adobe RoboHelp