We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
My organization (part of provincial government) uses Team Foundation Server 2015 to track version control. With RoboHelp 2017 and earlier, I used the Microsoft Team Foundation Server MSSCCI Provider to connect to TFS.
Am I missing the secret handshake that will allow me to connect to TFS in RoboHelp 2019 or is that functionality simply not available?
I raised this issue/question during the recent RH 2019 announcement/webinar and was informed that support for TFS is coming in a future update.
Thanks, RoboFan! That's good. I can play around getting the formatting set up until then.
I was happy to see the option of TFS in Update 2, but has anyone found any documentation yet on how to configure the TFS connector?
I'm also having this problem. Myself and another documenter share the same project. Everything works with Classic 2019 but it only half works with 2019: I'm able to get myself situated but my coworker cannot. All the information matches (local files, Visual Studio, RH) and we've even uninstalled and reinstalled RH on her computer.
Do you both have Update 14 installed? What exactly do you mean by "half works"?
We both have update 14, yes. By "half works" I mean that I have no problem making updates, checking in, checking out. My coworker's connection profile is identical to mine (except for the VS workspace) plus everything in her VS is the same as mine, but she does not have the option to check in when in RH. When she makes a change to a project, the check in button is always grayed out. Her error messages vary: sometimes it's not connected to the server or a different workspace is connected. To me, it feels like something might be up with the computer itself (it was previously used by another coworker), but I wanted to check this forum for anything we might have missed.
Given it works for you but not you colleague it does sound like something specific either to her login or computer.
I haven't connected to source control for a long time (and never with New UI) but there were a few things that used to cause issues that you could check. Remember, this was years and years ago, so I would hope none of them apply any more. 🙂
Dots in users names and thus in the file path, if you are getting your projects to Desktop or Documents or My Robohelp Projects. Since that incident, I've always 'got' my projects to something like c:\help\project to avoid this issue,.
If you have a dot and are saving the docs to one of those places, then the problem might be something different. Perhaps some of the source files or settings have a hard coded path containing your details. I imagine that could cause RH to freak out. Not sure how to determine that in New UI but start with the version control settings to see if there's anything obvious.
Multiple workspaces in TFS. My devs had a meltdown over this one. If people using RH had two workspaces in TFS RH would freak out (that's a technical term, because I can't remember what the symptom was, just that things broke.) Perhaps you only have one workspace and your colleague has multiple? Or can you set a default and you and your colleague have different defaults?
Hopefully someone with New UI TFS experience will jump in.