Skip to main content
Participant
May 22, 2009
Answered

.apj files and TFS Version Control

  • May 22, 2009
  • 1 reply
  • 1401 views

My team is using RoboHelp6 and Version Control on TFS (Microsoft Visual Studio 2008 Team Explorer and Source Control Explorer). Just opening the project in RoboHelp via version control will cause one of the .apj files (always the same one: rhtemplate.apj) to be checked out. In a multiuser setup with this file checked out another person can not do any edits. Is it necessary to have the .apj files under version control when they are not normally edited via RoboHelp after they are initially created? Is it possible to remove them from version control and still retain them in the RoboHelp project?

Thanks

Bob (No relation to John)

This topic has been closed for replies.
Correct answer Gravenstein

Hi Bob -

You've encountered a bug that we've been living with since X5. I'd be obliged if you'd report it, as I'd love to see Adobe finally fix it!

The problem is specific to rhtemplate.apj and, at least as far as RH6, does not affect the other apj files. All apj files, including rhtemplate.apj *do* need to go into source control. You are probably just going to have to learn to live with teh rhtemplate.apj annoyance.

I think the problem has to do with having multiple templates. RH will insist on checking RH template out to you when you do a save (either explicit or implicit). While you have the file checked out, other authors can open the project and do work, but they won't be able to close their project as long as you have the file checked out. As RSC administrator, I used to get a lot of calls requesting that I do an uncheckout of the rhtemplate.apj file so that Writer X could close his project! Now those calls rarely occur, because everyone has gotten into the habit of doing...

**THIS WORKAROUND**

1. Writer opens the project.

2. Writer immediately does a "Save All," which automatically checks out rhtemplate.apj.

3. Writer immediately does a "Check In All" or else explicitly checks in rhtemplate.apj.

4. That's it. The rhtemplate.apj file will behave itself for the rest of the session. (For that writer. Every writer who acesses the project needs to do this, every time.)

5. Next session, return to step 1.

HTH,

G

1 reply

Gravenstein
GravensteinCorrect answer
Inspiring
May 22, 2009

Hi Bob -

You've encountered a bug that we've been living with since X5. I'd be obliged if you'd report it, as I'd love to see Adobe finally fix it!

The problem is specific to rhtemplate.apj and, at least as far as RH6, does not affect the other apj files. All apj files, including rhtemplate.apj *do* need to go into source control. You are probably just going to have to learn to live with teh rhtemplate.apj annoyance.

I think the problem has to do with having multiple templates. RH will insist on checking RH template out to you when you do a save (either explicit or implicit). While you have the file checked out, other authors can open the project and do work, but they won't be able to close their project as long as you have the file checked out. As RSC administrator, I used to get a lot of calls requesting that I do an uncheckout of the rhtemplate.apj file so that Writer X could close his project! Now those calls rarely occur, because everyone has gotten into the habit of doing...

**THIS WORKAROUND**

1. Writer opens the project.

2. Writer immediately does a "Save All," which automatically checks out rhtemplate.apj.

3. Writer immediately does a "Check In All" or else explicitly checks in rhtemplate.apj.

4. That's it. The rhtemplate.apj file will behave itself for the rest of the session. (For that writer. Every writer who acesses the project needs to do this, every time.)

5. Next session, return to step 1.

HTH,

G

Participant
May 22, 2009

Thanks for your response! I will report it since it causes problems for our tech writer team which works from different time zones.

Bob (No relation to John)