RoboHelp 2019 - Version Control

[RoboFan]

How does version control work in RoboHelp 2019 for GIT??? In a multi-author environment, will it automatically check out and lock files that are being edited? Or will users have to manually notify each other what they're working on and/or manually merge changes when there are conflicts?

Also, is there a plan - and timeline (and if so, when?) - to deliver version control via RoboSource Control (3.1 or maybe RSC 2019????) and Microsoft SCC API (for example, Microsoft SQL Server 2017 Express)?

[RoboFan]

Based on information provided during Adobe's recent RoboHelp 2019 announcement/release webinar:

• RoboSource Control is not supported in RoboHelp 2019.

• Version control via TFS is supposed to be provided in a future RoboHelp 2019 update.

[vivek_k]

TFS support is now available via Update 2 of RH 2019. See the full list of improvements in update 2 Issues fixed in Adobe RoboHelp (2019 release)

[susanf1]

I did the following to make RoboHelp Source work with Azure DevOps Git...

To setup source control with Robohelp, perform the following actions:

1. Create a Master repository location in AzureDevOps.
2. Clone the Master repository location within your local machine.
3. Set your Robohelp Project file to the Master repository location within your
   local machine.
4. Save your Project file.
5. In Visual Studio 2019, Team Explorer, click Show Folder View.
6. Right click the .xpj file and then click Open With.
7. In the Open With dialog, click Add.
8. Browse to the Robohelp.exe file to select it.
9. Highlight Robohelp in the Open With window and then click Default.
   1. Right click inside the Solutions Explorer and then select Go to Git Changes from the shortcut menu.
   2. Highlight the appropriate files and then enter a Branch comment.
   3. Select Commit All and Push to check-in the files to the server.
   4. Suggestion:  Use Staged for specific files.

[Germanedge Solutions GmbH]

@susanf1 Is this also working for GitHub or just for Azure DevOps