某些 Creative Cloud 应用程序、服务和功能在中国不可用。
Before creating a Team Foundation Server connection profile, do the following:
- Set up Team Foundation Version Control on your machine. For more information, see Microsoft Help.
- In RoboHelp, choose Edit > Preferences. In the Application Settings dialog box, click Version Control and specify the complete path of the tf.exe binary in the Team Foundation Client field. The tf.exe binary is available in the Visual Studio or Team Explorer install directory on your computer. An example path:
C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/Common7/IDE/CommonExtensions/Microsoft/
TeamFoundation/Team Explorer/TF.exe
Opomba:
RoboHelp supports the tf.exe file version 14.102 and above.
If your system language is other than English, a workaround is needed to support the connection to Team Foundation Server. The folder that contains tf.exe also contains subfolders for different languages. Remove or rename the subfolder corresponding to your system language so that tf.exe defaults to the English version. For example, if your system language is French, remove or rename the 'fr' subfolder.
-
Create a team project on Team Foundation server to establish a repository for source content, where teams can plan, track progress, and collaborate.
Opomba:
Ensure that your system user account (through which RoboHelp is being run) has adequate permissions to access the created team project. For information about modifying user permissions, see Microsoft Help.
-
In the Workspace field, specify a workspace name. This workspace is created at the path specified in the Local Path field.
Workspace is your local copy of the project. You can create content locally in RoboHelp and then check it in to Team Foundation Server. For more information about workspace, see Microsoft Help.
Opomba:
Ensure that your system user account (through which RoboHelp is being run) has adequate permissions to create a workspace for the team project.
RoboHelp works only with local workspaces. For information about using a local workspace and setting the default workspace type for your project collection, see Microsoft Help.
-
In the Local Path field, specify a path on your computer that maps to the team project.
If the connection profile is to be used to upload the currently open RoboHelp project to Team Foundation Server, specify the folder containing the project or any of its parent folders. This folder is mapped to the team project contents on the server.
Otherwise, to use the connection profile to download a team project, provide the path to an empty local folder in which the project is to be downloaded.
-
In RoboHelp, choose Collaborate > Open Connection and select a Team Foundation Server connection profile.
Opomba:
For first-time connections to the Team Project Collection URL, RoboHelp prompts for your password and saves it in the system Credential Manager for subsequent use. If you changed the password recently, delete or update the corresponding record from the Credential Manager to avoid password error prompts. The record is stored in this format:
team:<server>|<user>
If RoboHelp does not find a matching record in the system Credential Manager, it prompts for the password again. For more information about system Credential Manager (Windows), see Microsoft Help. -
In the Open dialog box, select a RoboHelp project file (.rhpj) and click Open.
RoboHelp opens the project file.
Opomba:
When you open a RoboHelp project for the first time using these steps, connection information is stored inside the project for subsequent use. So directly open the project using one of the ways described in Open a project.
-
Add content to or edit a topic. You can quickly begin editing files when your network connection is unavailable or unreliable. As RoboHelp uses only local workspaces, you need not explicitly check out files before editing.
-
Opomba:
If the file you are trying to check in is changed by another user on the server, the check-in fails. You are prompted to resolve the conflict between the local and server versions. After all conflicts are resolved, check in the file again.
You can lock files in the Contents panel to temporarily prevent changes by other users on the server. This is helpful if you want to change a file in your workspace and then check it in without being forced to resolve merge conflicts. Only one user at a time can lock a file.
when locked by other users and as 
when locked by you. -
To add a project, choose Collaborate > Add Project and select a Team Foundation Server connection profile.
The local path in the profile must contain the current project. For more information, see Step 8 in Create a Team Foundation Server connection profile.
The Check-in dialog box opens.
-
Check in the required files as described in Work with files under version control.
-
If you want to delete the local workspace also, select the Delete any source control information from the local folder also field in the Confirm dialog box.
Pozor:
Check-in all your changes before deleting the workspace and unlock locked files that are not being checked in.
Opomba:
The delete workspace operation fails if the current system user does not have delete permission.
-
Click Ok.
As soon as the connection is removed, RoboHelp reopens the project, and the Add Project option in Collaborate menu becomes available. To add the project again, see Add a project to Team Foundation Server.