Importing a Project From Team Foundation Server

This topic focuses on importing a Flare project from source control. You might use this method, for example, if you are working on a multi-author project and another member of the team has placed the Flare project in Microsoft Team Foundation Server.

How to Import a Project From Team Foundation Server

  1. Do one of the following, depending on the part of the user interface you are using:
    • Ribbon Select File > New Project > Import Project.

    • Source Control Explorer From the View ribbon, open the Source Control Explorer. From the drop-down, select the Home pane. Click Import Project.

    The Import Project from Source Control Wizard dialog opens.

  2. From the drop-down, select Microsoft Team Foundation Server.
  3. In the Server field, enter the name of the computer or the IP address of the server. You can also click The browse ellipsis button opens to more options. to select a "Team Project Collection." If you click this button, the Select Team Foundation Server Project Collection dialog opens, and you can do the following.

    1. To add a server, click . The Add Team Foundation Server dialog opens.
    2. Enter the name or URL of the server.
    3. Enter the path and port number.
    4. Select the protocol (HTTP or HTTPS).

    Note You may need to obtain this information from your system administrator. Click OK in the dialogs until you return to the main wizard page.

    Note If you run into issues in this dialog, chances are your user permissions do not have access to all of the collections on the TFS server. Please try to enter in the server/collection path manually.

  4. Next to the Team Project field, click The browse ellipsis button opens to more options.. If the Log In dialog opens, complete the User name and Password fields.
  5. Click on the Team Foundation project.
  6. Click Next.
  7. Next to the Project file field, click Browse. The Browse Source Control Files dialog opens.

  8. Find and click on the Flare project file (FLPRJ) that you want to import. (You may need to log in with your user name and password.)
  9. Click OK.
  10. Click Next.
  11. In the Project name field, the name of the project being imported is displayed. It is recommended that you leave the name as it is, especially if you are working with other authors on the project. However, you can enter a different project name if you want.
  12. In the Project folder field, either accept the default location for the new project or click The browse ellipsis button opens to more options. to browse for and select a folder.
  13. Click Finish. The project is imported and loaded into Flare

Note When a project is dual bound to Central and a non-Git third-party provider, keep the following in mind if you (i.e., the second user) want to access this setup. After importing the project from Perforce Helix Core, Subversion, or Team Foundation Server, you will have to re-bind the project to Central. In Flare’s MadCap Central window pane, click to upload (or bind) the project to Central. In the Bind Project dialog, it is important to enter the exact name of the project as it currently exists on Central. When you click OK, a message displays asking if you want to bind to the existing project. Select Yes. This re-establishes the existing Flare/Central connection; note that it does not create a new binding. See Dual-Bound Projects.

Note If you want to import a project from source control, you can alternatively open the project file from another location (e.g., a server location), and then use Flare's bind detection functionality to automatically apply available source control bindings to the project. See Options Dialog.