18 April 2011
To follow this article, you should have a basic understanding of:
Team Foundation Server (TFS) is a Microsoft product offering source control, data collection, reporting, and project tracking. It is intended for collaborative handling of any project.
RoboHelp 9 integrates seamlessly with TFS 2010, TFS 2008, and TFS 2005. For the steps described in this article, Team Foundation Server 2010 has been used.
To integrate Team Foundation Server with your RoboHelp project, you must install and configure the following components:
Configure the server
After Team Foundation Server is installed and running, start Team Foundation Administration Console as an administrator. Configure Team Foundation Server settings and create a team project collection. Client machines connect to the team project collection and add RoboHelp projects to the team projects in a selected collection.
To create team projects, launch Visual Studio on your server machine as an administrator and connect it to Team Foundation Server:
Configure the client
In this section, you will connect Visual Studio to Team Foundation Server.
Launch Visual Studio from the client machine and connect to Team Foundation Server by clicking Team > Connect to Team Foundation Server. Provide your Team Foundation Server name and select the team project collection name and the team project(s).
Install Team Foundation Server MSSCCI Provider on the client machine to enable integrated use of Team Foundation version control with RoboHelp.
Verify the installation
Verify that Microsoft Team Foundation Server MSSCCI Provider is listed as a source provider in the registry (HKLM > Software > SourceCodeControlProvider >InstalledSCCProviders).
Add a RoboHelp project to TeamFoundation Server
In this example, the team project collection name is TeamCollection, the team project name is Demo, and the RoboHelp project name is DemoProject.
Folder location: Choose the team project.
Name for the solution folder: Provide the name for the folder that will store the RoboHelp project files. By default, the RoboHelp project name is used.
Local path: Local path is automatically set to the current project path.
Local workspace: You can choose an existing workspace or create a new workspace by clicking Add.
Now the files and folders of the current project are added to the server and you can perform the version control operations, such as checkin and checkout, on your project.
Get a RoboHelp project from TeamFoundation Server
To get a project from Team Foundation Server, make sure that you have the server name, folder details, and the appropriate access rights.
Provide the server name and folder details.
Choose a workspace from the Local workspace list, which will autofill the local path for the chosen workspace. You can browse to the local path if you're opening this project for the first time.
You can now open the .xpj file of the project, and the version-controlled project will be opened in RoboHelp.
Do we need RoboSource Control to be installed?
Absolutely not. Team Foundation Server is another version control system. RoboSource Control installation is required only when RoboHelp integrates with RoboSource Control version control system. RoboHelp is capable of integrating with any MSSCCI- compliant version control system.
What happens if you add the project to an incorrect location in Team Foundation Server?
Team Foundation Server maintains a mapping of the project directories of a machine to corresponding server paths (directories) through its workspaces. This mapping is created automatically when we add a RoboHelp project to Team Foundation Server. So, if you have added the RoboHelp project to the wrong server path, do the following to add it again to the correct location:
What if you opened a project from Team Foundation Server at the incorrect local path?
Do the following steps:
If you face problems in integrating an earlier version of a Visual Studio client with an advanced version of Team Foundation Server, check the following articles: