First draft of the updated TFVC guidance.

Author: jmatthiesen

mac/media/tfvc-install.png

@@ -1,9 +1,9 @@
 ---
 title: "Team Foundation Version Control (TFVC)"
-description: "Connecting to Team Foundation Server or Azure DevOps Services with Team Foundation Version Control (TFVC)."
+description: "Connecting from Visual Studio for Mac to Team Foundation Server/Azure DevOps with Team Foundation Version Control (TFVC)."
 author: conceptdev
 ms.author: crdun
-ms.date: 09/05/2018
+ms.date: 04/04/2019
 ms.topic: article
 ms.technology: vs-ide-general
 ms.assetid: 52D3D26A-4D01-4FD1-AAA1-AE7D7BD39746
@@ -12,33 +12,113 @@ ms.assetid: 52D3D26A-4D01-4FD1-AAA1-AE7D7BD39746
 # Connecting to Team Foundation Version Control
 
 > [!NOTE]
-> Team Foundation Version Control support is currently in preview and some functionality is not yet fully working. We'd love feedback from you on any issues at [Developer Community](https://developercommunity.visualstudio.com/spaces/41/index.html). More changes are still to come!
+> For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC). 
+Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. To learn more about using Git with TFS/Azure DevOps, see the [Setting up a Git Repository](./set-up-git-repository) article.
 
-Azure Repos provides two models of version control: Git, which is distributed version control, and Team Foundation Version Control (TFVC), which is centralized version control. This article provides an overview and a starting point for using TFVC with Visual Studio for Mac.
+Azure Repos provides two models of version control: Git, which is distributed version control, and Team Foundation Version Control (TFVC), which is centralized version control.
+
+Visual Studio for Mac provides full support for Git repositories, but requires some workarounds to work with TFVC. If you're using TFVC for version control today, here are some solutions you can use to access your source code hosted in TFVC.
+
+* [Use Visual Studio Code and the Azure Repos extension, for a graphical UI](#use-visual-studio-code-and-the-azure-repos-extension)
+* [Connect to your repo using the Team Explorer Everywhere Command Line Client (TEE-CLC)](#connecting-using-the-team-explorer-everywhere-command-line-client)
+* [Connect to TFVC using the (unsupported) Team Foundation Version Control extension for Visual Studio for Mac](#connect-to-tfvc-using-the-team-foundation-version-control-extension)
+
+The rest of this article walks you through the options listed above.
 
 ## Requirements
 
-* Visual Studio Community, Professional, or Enterprise for Mac version 7.5 or later.
-* Azure DevOps Services, or Team Foundation Server 2013 and later.
-* A project in Azure DevOps Services or Team Foundation Server, configured to use Team Foundation Version Control.
+* Visual Studio Community, Professional, or Enterprise for Mac version 7.8 or later.
+* Azure DevOps Services, Team Foundation Server 2013 and later, or Azure DevOps Server 2018 and later.
+* A project in Azure DevOps Services or Team Foundation Server/Azure DevOps Server, configured to use Team Foundation Version Control.
+
+## Use Visual Studio Code and the Azure Repos extension
+
+If you like to work with a graphical interface for managing you local version control, then the Azure Repos extension for Visual Studio Code provides a supported solution from Microsoft. To get started, download [Visual Studio Code](https://code.visualstudio.com) and then learn how to [configure the Azure Repos extension](https://marketplace.visualstudio.com/items?itemName=ms-vsts.team).
+
+## Connecting using the Team Explorer Everywhere Command Line Client
+
+If you're comfortable using the macOS Terminal, then the Team Explorer Everywhere Command Line Client (TEE-CLC) provides a supported way to connect to your source in TFVC.
+
+Special thanks to Chris Pilcher, a developer in our community, who's [original instructions for the TEE-CLC](https://gist.github.com/chris-pilcher/a3f14eb081d7ab983e5c) formed the basis of this section.
+
+### Setting up the TEE-CLC
+
+There are two ways to get setup with the TEE-CLC.
+
+1. Use Homebrew to install the client.
+1. Download and manually install the client.
+
+The easiest solution is **using HomeBrew**, which is a package manager for macOS. To install using this method:
+
+1. Launch the macOS Terminal application.
+1. Install Homebrew using the Terminal and the instructions on the [Homebrew home page](https://brew.sh/).
+1. Once Homebrew is installed, run the following command from your Terminal: `brew install tee-clc`
+
+To **setup the TEE-CLC manually**:
+
+1. [Download the latest version of the tee-clc](https://github.com/Microsoft/team-explorer-everywhere/releases) from the releases page of the Team Explorer Everywhere GitHub repo (e.g. tee-clc-14.134.0.zip at the time of this writing).
+1. Extract the content of the .zip to a folder on disk.
+1. Open the macOS Terminal app and use the `cd` command to switch to the folder you used in the previous step.
+1. From within the folder, run the command `./tf` to test that the command line client can run, you may be prompted to install Java or other dependencies.
+
+Once the TEE-CLC is installed, you can run the command `tf eula` to view and accept the license agreement for the client.
 
-## Installation
+Finally, to authenticate with your TFS/Azure DevOps environment, you'll need to create a personal access token on the server. Learn more about [authenticating with personal access tokens](https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/pats?view=azure-devops). 
 
-In Visual Studio for Mac, choose **Visual Studio > Extensions** from the menu. In the **Gallery** tab, select **Version Control > Team Foundation Version Control for TFS and VSTS** and click **Install**:
+### Using the TEE-CLC to connect to your repo
+
+To connect to your source code, you first need to create a workspace using the `tf workspace` command. For example, the following commands connect to an Organization in Azure DevOps Services called "MyOrganization": 
+
+```
+export TF_AUTO_SAVE_CREDENTIALS=1
+tf workspace -new MyWorkspace -collection:https://dev.azure.com/MyOrganization
+```
+
+The `TF_AUTO_SAVE_CREDENTIALS` environment setting is used to save your credentials so you aren't prompted to enter them multiple times. When prompted for a user name, use the personal access token you created in the previous section and use a blank password.
+
+Now, to create a mapping of your source files to a local folder, you'll use the `tf workfold` command. The following example will map a folder named "WebApp.Services" from the "MyRepository" TFVC project and set it up to be copied into the local ~/Projects/ folder (i.e. a "Projects" folder in the current users's home folder).
+
+```
+tf workfold -map $/MyRepository/WebApp.Services -workspace:MyWorkspace ~/Projects/
+```
+
+Finally, you use the following command to get the source files from the server and copy them locally:
+
+```
+tf get
+```
+
+### Committing changes using the TEE-CLC
+
+After you've made changes to your files in Visual Studio for Mac, you can switch back to the Terminal to check in your edits. The `tf add` command is used to add files to the list of pending changes to be checked-in and the `tf checkin` command performs the actual check-in to the server. The `checkin` command includes parameters to add a comment or associate a related work item. In the following code snippet, all files in a `WebApp.Services` folder are added, recursively, to the checkin. Then, the code is checked in with a comment and associated with a work item with the ID "42".
+
+```
+cd WebApp.Services
+tf add * /recursive
+tf checkin -comment:"Replaced 'Northwand' typos with the correct word Northwind" -associate:42
+```
+
+To learn more about the commands mentioned here, or others, you can use the following command from the Terminal:
+
+`tf help`
+
+## Connect to TFVC using the Team Foundation Version Control extension
+
+In the Visual Studio for Mac Extension gallery, there is a Team Foundation Version control extension that offers limited support to connect to TFVC. The extension is not supported and has several known issues, so your experience may vary when using it.
+
+To install the extension, launch Visual Studio for Mac and choose the **Visual Studio > Extensions** menu. In the **Gallery** tab, select **Version Control > Team Foundation Version Control for TFS and Azure DevOps** and click **Install...**:
 
 ![Extension manager](media/tfvc-install.png)
 
 Follow the prompts to install the extension. Once it's installed, restart the IDE.
 
-## Updating the extension
+### Updating the extension
 
 Updates to the TFVC extension are made periodically. To access updates, choose **Visual Studio > Extensions...** from the menu and select the **Updates** tab. Select the extension in the list and press the **Update** button:
 
-![Extension manager showing update](media/tfvc-update.png)
-
 Press **Install** on the next dialog to uninstall the old package and install the new one.
 
-## Using the add-in
+### Using the add-in
 
 Once the extension is installed, select the **Version Control > TFS/Azure DevOps > Open from Remote Repository** menu item.
 
@@ -48,19 +128,19 @@ Choose either VSTS or Team Foundation Server to get started and press **Continue
 
 ![Connect with a Server](media/tfvc-choose-server-type-devops.png)
 
-### Azure Repos Authentication
+#### Azure Repos Authentication
 
 When you select a project that is hosted on Azure Repos, you're prompted to enter your Microsoft account details:
 
 ![Connect with Azure Repos](media/tfvc-vsts-login.png)
 
-### TFS Authentication
+#### TFS Authentication
 
 To connect to TFS, enter the server details and your account credentials. Enter a domain to use NTLM authentication, otherwise leave blank to use basic authentication. Select **Add Server**:
 
 ![Sign in to a TFS Server](media/tfvc-login.png)
 
-## Selecting a project
+### Selecting a project
 
 Once you've successfully authenticated, you can see a list of repositories that are associated with the account in the **Open from Source Control** dialog:
 
@@ -73,7 +153,7 @@ This dialog is organized with the following nodes:
 
 At this point, you can search and filter by the name of a project or organization.
 
-### Adding a new server
+#### Adding a new server
 
 To add a new server to the list, press the **Add Host** button on the **Open from Source Control** dialog:
 
@@ -83,7 +163,7 @@ Select the provider from the list, and enter your credentials:
 
 ![Dialog showing option for source control provider](media/tfvc-add-new-creds-devops.png)
 
-## Creating a new workspace
+### Creating a new workspace
 
 To start working with a project, you need to have a _workspace_. If you don't already have a workspace, you can create one from the **Workspace** combobox in the **Open from Source Control** dialog:
 
@@ -93,7 +173,7 @@ Set the name and local path for your new workspace and select **Create Workspace
 
 ![Entering a name and local path for the new workspace](media/tfvc-local-workspace.png)
 
-## Using the Source Code Explorer
+### Using the Source Code Explorer
 
 Once you've created a workspace and mapped your project, you can start working with the _Source Code Explorer_.
 
@@ -113,7 +193,7 @@ Many of these actions are available through context actions on the project:
 
 ![Context menu actions for a project](media/tfvc-sourcecode-actions.png)
 
-## Managing workspaces
+### Managing workspaces
 
 If you haven't already created a workspace, as described in the [Creating a workspace](#creating-a-new-workspace) section, you'll notice that the Source Code Explorer is empty:
 
@@ -140,9 +220,9 @@ Once your workspace is set up, it can be changed or removed by clicking the **Ma
 
 ![Manage Workspaces](media/tfvc-workspace4.png)
 
-## Troubleshooting
+### Troubleshooting
 
-### Problems using basic authentication
+#### Problems using basic authentication
 
 The following options can be used to authenticate with a server:
 
@@ -162,26 +242,26 @@ To use basic authentication it is necessary to enable **Alternative authenticati
 
     ![Policy settings option selected](media/tfvc-auth.png)
 
-### I do not see anything in TFVC
+#### I do not see anything in TFVC
 
 To set up Team Foundation Version Control (TFVC) on your dev machine, you **must** create a workspace, as described in the [Managing workspaces](#managing-workspaces) section.
 
 In Source Control Explorer, press the **Manage Workspaces** Button. Follow the steps to map the project to a folder on your dev machine.
 
-### I do not see any / all of my projects
+#### I do not see any / all of my projects
 
 After authenticating you should see the list of projects. By default, only TFS projects are shown. To see other types of projects, check the "See all projects" box.
 
 Keep in mind that projects that are on the server will not appear if you don't have the correct privileges.
 
-#### I am getting the error "Cannot create the workspace. Please, try again"
+##### I am getting the error "Cannot create the workspace. Please, try again"
 
 When trying to [create a new workspace](#creating-a-new-workspace), you should make sure the following conditions are met:
 
 - No use of invalid characters in the workspace name.
 - The name must be less than 64 characters.
 - The local path cannot be used by any other workspaces.
 
-## See also
+### See also
 
 - [Develop and share your code in TFVC using Visual Studio (on Windows)](/azure/devops/repos/tfvc/share-your-code-in-tfvc-vs)