Binding a Project to Perforce Helix Core

Use the following steps if you have already created a Lingo project and want to bind ("connect") it to Perforce Helix Core. You can also automatically detect existing source control bindings if your project has been previously connected to Helix Core.

Note The following steps show how to bind a project using the Lingo interface. It is also possible to bind a project outside of Lingo (e.g., using Git Bash). If you decide to do this, you should be aware of some additional aspects of source control, such as bind detection and disabling providers. See Bind Detection, Disabling Providers, and Unbinding Providers—Perforce Helix Core.

How to Bind a Project Using the Project Properties Dialog

  1. Open the project.
  2. Select File > Project Properties. The Project Properties dialog opens.
  3. Select the Source Control tab.
  4. Click Bind Project. The Bind Project dialog opens.
  5. From the drop-down, select Perforce Helix Core.
  6. In the Server field, enter the server address.
  7. Next to the User field, click The browse ellipsis button opens to more options..
  8. Select a user and click OK. (Users are set up separately in Perforce Helix Core.)
  9. From the Type drop-down, select whether you want to bind to a stream or a depot. A depot contains multiple streams.

    If Binding to a Stream

    1. Next to the Stream field, click New.

      If the Log In dialog opens, complete the User name and Password fields and click OK.

      The New Stream dialog opens.

    2. From the Stream Type drop-down, select the type of stream you want to use. Most streams are mainline streams.
    3. Next to the Streams Depot field, click Browse.

      The Browse Depots dialog opens.

    4. Select a depot. This is essentially a folder or directory in Perforce Helix Core that contains multiple streams, one of which will be your Lingo files.
    5. Click OK.
    6. (Optional) In the New Stream dialog, you can complete any of the other fields as necessary. For information about these fields, please refer to the documentation provided with Perforce Helix Core.
    7. Click OK.

    If Binding to a Depot

    1. Next to the Depot field, click New, or select an existing depot using the drop-down arrow.

      If you clicked New, the New Depot dialog opens.

    2. In the Name field, enter a name for the depot.
    3. (Optional) In the Description field, enter a description for the depot.
    4. Click OK.
    5. Next to the Path field, click The browse ellipsis button opens to more options..

      If the Log In dialog opens, complete the User name and Password fields and click OK.

      The Browse Source Control Folders dialog opens.

    6. Select the location where you want to bind the project.
    7. Click OK.
  10. (Optional) In the Comment field, you can enter any internal comments.
  11. (Optional) If you want the files in the project to be checked out when you are finished, click Keep files checked out.
  12. In the Bind Project dialog, click OK.
  13. If the Log In dialog opens, complete the User name and Password fields and click OK. Copies of the Lingo files are created and added to the folder you specified.
  14. In the Project Properties dialog, click OK. The project is connected to Perforce Helix Core, and you can now submit files and check them out as necessary.

How to Bind a Project Using the Explorer

  1. Open the project.
  2. Select View > Source Control Explorer. The Source Control Explorer opens.
  3. From the drop-down or the Home pane, select Settings. The Settings pane opens.

  4. Click Bind. The Bind Project dialog opens.
  5. From the drop-down, select Perforce Helix Core.
  6. In the Server field, enter the server address.
  7. Next to the User field, click The browse ellipsis button opens to more options..
  8. Select a user and click OK. (Users are set up separately in Perforce Helix Core.)
  9. From the Type drop-down, select whether you want to bind to a stream or a depot. A depot contains multiple streams.

    If Binding to a Stream

    1. Next to the Stream field, click New.

      If the Log In dialog opens, complete the User name and Password fields and click OK.

      The New Stream dialog opens.

    2. From the Stream Type drop-down, select the type of stream you want to use. Most streams are mainline streams.
    3. Next to the Streams Depot field, click Browse.

      The Browse Depots dialog opens.

    4. Select a depot. This is essentially a folder or directory in Perforce Helix Core that contains multiple streams, one of which will be your Lingo files.
    5. Click OK.
    6. (Optional) In the New Stream dialog, you can complete any of the other fields as necessary. For information about these fields, please refer to the documentation provided with Perforce Helix Core.
    7. Click OK.

    If Binding to a Depot

    1. Next to the Depot field, click New, or select an existing depot using the drop-down arrow.

      If you clicked New, the New Depot dialog opens.

    2. In the Name field, enter a name for the depot.
    3. (Optional) In the Description field, enter a description for the depot.
    4. Click OK.
    5. Next to the Path field, click The browse ellipsis button opens to more options..

      If the Log In dialog opens, complete the User name and Password fields and click OK.

      The Browse Source Control Folders dialog opens.

    6. Select the location where you want to bind the project.
    7. Click OK.
  10. (Optional) In the Comment field, you can enter any internal comments.
  11. (Optional) If you want the files in the project to be checked out when you are finished, click Keep files checked out.
  12. In the Bind Project dialog, click OK.
  13. If the Log In dialog opens, complete the User name and Password fields and click OK. Copies of the Lingo files are created and added to the folder you specified. The project is connected to Helix Core, and you can now submit files and check them out as necessary.

What’s Noteworthy?

Tip If you are having difficulty binding your project, try binding to a brand new directory in your source control provider. You should also ensure that the directory on your local machine (and its parent directories) is not already mapped to source control, as this may cause issues with binding.

Note You can also bind a new Lingo project to source control while creating it. See Creating Projects.