Skip to main content
August 11, 2015
Question

Roobohelp 9 integration with TFS 2013

  • August 11, 2015
  • 1 reply
  • 796 views

Hi,

I was working on Robohelp 9 with Team foundation server 2012 and I had also installed the MSSCCI provider. Now I've moved on to Team foundation server 2013.

Is it possible to integrate Robohelp projects with TFS 2013? What are the necessary installations to do so?

Kindly suggest your views asap

Thanks,

Dipali


This topic has been closed for replies.

1 reply

Peter Grainge
Community Expert
Community Expert
August 11, 2015

Thread moved to Source Control forum.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Willam van Weelden
Inspiring
August 12, 2015

Requirements are the same as for TFS 2013. You need a Visual Studio installation (The Integrated Shell with TFS client is enough) and the MSSCCI provider for the TFS client version you have installed. You can connect to TFS 2013 server with a VS2012 installation, so nothing needs to change on your end. (Unless the new server version requires you to update your workspace. In that case you may have to relink the project the first time you open it in RoboHelp.)

October 19, 2015

Hi,

I'm able to do the check-ins, but the above two issues (mentioned in my last post) are still not resolved.

One more issue:

We have installed the licensed version of Robohelp 9 on another machine. The MSSCCI provider provider 2013 for 64 bit, TFS 2013 and Power tools are also installed. The TFS mapping is done properly.

The mapping is available outside the projects, i.e. we can check-out the files in the mapped project folder but if we open the Robohelp project, the TFS mapping is not available in side the project. We are getting the below error  and there is no option of source control on any for Check-ins.

We cannot do the operations like creating windows, layouts, ToC, etc due to this issue.

Kindly suggest if you know any solution to overcome this issue. We have a scheduled release, so need to resolve this issue ASAP.

Thanks,

Dipali


Yessss!

I could solve one issue!

Instead of MSSCCI provider 64 bit, we should install MSSCCI provider 32 bit.