Skip to main content
A
Anonymous
September 11, 2014
Answered

RoboSource Control or similar

  • September 11, 2014
  • 1 reply
  • 714 views

Hello.

I am using RH10 and need to set up Source Control - it doesn't have to be RoboSource Control but the company I contract for is moving away from SharePoint so I can't use that. Any advice on this area will be gratefully received.


I think I understand correctly that I need to ask a DB or Technical Support expert to set up an SQL database for me. That should hopefully prove to be straightforward.

However, when I currently open the Connection List in RH10 (File > Version Control > Add To Version Control), I can only see a connection to SharePoint. There is no Create button to enable me to add a new link for when the new database is set up for me.

Can anyone advise what I need to do to get this working as described in the RH10 Online Help?

Thanks.

Philip

This topic has been closed for replies.
Correct answer Willam van Weelden

Hi,

Adding RoboHelp to source control requires a little more work, since you need to install the correct components to make everything work together. What you need to do depends on the source control system you want to use. You can find instructions for several source control systems on: http://www.adobe.com/devnet/robohelp.html

On which system to choose, I recently answered a similar question. I can't find the post anymore, but here was my answer. I hope this gets you started. Please post back if you have any further questions.

With source control, the easiest option is usually the best. Here are the three global options:

  • Use SharePoint for version control: This is very easy to set up and if you are a SharePoint administrator you don't need any IT guys helping out. This is by far the simplest way to go.
    • You will need SharePoint 2010 or 2013. SharePoint 365 doesn't work.
    • If you have SharePoint there is no additional cost involved.
  • Use RoboSourceControl: This is the source control system included in RoboHelp itself.
    • It works rather well, but it is a pain to set up. You need a database (and a server to host that) and connect every team member to the source control system.
    • You will require the support of an IT guy. I normally advise against this system because it is so problematic to set up.
    • There is no additional cost for this option.
  • Use the source control system your developers use. If your developers use a source control system that support the Microsoft SCC API, you can use that source control system.
    • The advantage of these systems is that they are generally more rubust than SharePoint, they are optimized for speed and they offer many advanced features that SharePoint lacks such as check in policies, integration with issue trackers, reports, etc.
    • The knowlegde of this system is already in house so no consulting will be required for this side.
    • You will need the support of the manager of the source control system and most likely also the support of an IT guy.
    • You will be able to get a complete version of a project from a specific label/date/etc at once. With SharePoint you can only get older versions of individual files.
    • Depending on your licensing structure, this option may require more additional licenses.
My advise is to choose for either SharePoint or the source control your developers use. Your management might prefer to have all content in a single repository and so choose the third option. In any way, backups will be made centrally and you will have the capability of comparing files between different versions.

If you want to quickly get older versions and have advanced reports on check in history, number of changes, etc. Than the third option is the way to go. If you only need older versions of single files and you want to get it done tomorrow, go for SharePoint.

You can always later change the source control system you use. But you will lose all history if you do this.

Please note that comparing files may require an additional free tool such as WinMerge (http://winmerge.org/)

Kind regards,

Willam

1 reply

Willam van Weelden
Willam van WeeldenCorrect answer
Inspiring
September 11, 2014

Hi,

Adding RoboHelp to source control requires a little more work, since you need to install the correct components to make everything work together. What you need to do depends on the source control system you want to use. You can find instructions for several source control systems on: http://www.adobe.com/devnet/robohelp.html

On which system to choose, I recently answered a similar question. I can't find the post anymore, but here was my answer. I hope this gets you started. Please post back if you have any further questions.

With source control, the easiest option is usually the best. Here are the three global options:

  • Use SharePoint for version control: This is very easy to set up and if you are a SharePoint administrator you don't need any IT guys helping out. This is by far the simplest way to go.
    • You will need SharePoint 2010 or 2013. SharePoint 365 doesn't work.
    • If you have SharePoint there is no additional cost involved.
  • Use RoboSourceControl: This is the source control system included in RoboHelp itself.
    • It works rather well, but it is a pain to set up. You need a database (and a server to host that) and connect every team member to the source control system.
    • You will require the support of an IT guy. I normally advise against this system because it is so problematic to set up.
    • There is no additional cost for this option.
  • Use the source control system your developers use. If your developers use a source control system that support the Microsoft SCC API, you can use that source control system.
    • The advantage of these systems is that they are generally more rubust than SharePoint, they are optimized for speed and they offer many advanced features that SharePoint lacks such as check in policies, integration with issue trackers, reports, etc.
    • The knowlegde of this system is already in house so no consulting will be required for this side.
    • You will need the support of the manager of the source control system and most likely also the support of an IT guy.
    • You will be able to get a complete version of a project from a specific label/date/etc at once. With SharePoint you can only get older versions of individual files.
    • Depending on your licensing structure, this option may require more additional licenses.
My advise is to choose for either SharePoint or the source control your developers use. Your management might prefer to have all content in a single repository and so choose the third option. In any way, backups will be made centrally and you will have the capability of comparing files between different versions.

If you want to quickly get older versions and have advanced reports on check in history, number of changes, etc. Than the third option is the way to go. If you only need older versions of single files and you want to get it done tomorrow, go for SharePoint.

You can always later change the source control system you use. But you will lose all history if you do this.

Please note that comparing files may require an additional free tool such as WinMerge (http://winmerge.org/)

Kind regards,

Willam

A
Anonymous
September 12, 2014

Hello Willam,

Thank you so much for your detailed reply. Very much appreciated.

From what you have said, I think the source control that our developers use is the best option. I do not know what that is yet but there are many people who will be able to assist.

Regards

Philip

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices