|
| 1 | +--- |
| 2 | +title: "Tutorial: Open a project from a repo in Visual Studio 2017" |
| 3 | +description: "Learn how to open a project in a Git or Azure DevOps repository by using Visual Studio 2017." |
| 4 | +ms.custom: "get-started" |
| 5 | +ms.date: 01/25/2021 |
| 6 | +ms.technology: vs-ide-general |
| 7 | +ms.prod: visual-studio-windows |
| 8 | +ms.topic: tutorial |
| 9 | +author: TerryGLee |
| 10 | +ms.author: tglee |
| 11 | +manager: jillfra |
| 12 | +dev_langs: |
| 13 | + - CSharp |
| 14 | +ms.workload: |
| 15 | + - "dotnet" |
| 16 | + - "dotnetcore" |
| 17 | +monikerRange: vs-2017 |
| 18 | +--- |
| 19 | +# Tutorial: Open a project from a repo in Visual Studio 2017 |
| 20 | + |
| 21 | +In this tutorial, you'll use Visual Studio 2017 to connect to a repository for the first time and then open a project from it. |
| 22 | + |
| 23 | +> [!TIP] |
| 24 | +> There's a new, more fully integrated way to connect with a GitHub repo in [Visual Studio 2019](https://visualstudio.microsoft.com/downloads). For more information, see the [**New Git experience in Visual Studio 2019**](../ide/git-with-visual-studio.md?view=vs-2019&preserve-view=true) page. |
| 25 | +
|
| 26 | +## Open a project from a GitHub repo by using Visual Studio 2017 |
| 27 | + |
| 28 | +1. Open Visual Studio 2017. |
| 29 | + |
| 30 | +1. From the top menu bar, select **File** > **Open** > **Open from Source Control**. |
| 31 | + |
| 32 | + The **Team Explorer - Connect** pane opens. |
| 33 | + |
| 34 | +  |
| 35 | + |
| 36 | +1. In the **Local Git Repositories** section, select **Clone**. |
| 37 | + |
| 38 | +  |
| 39 | + |
| 40 | +1. In the box that says ***Enter the URL of a Git repo to clone***, type or paste the URL for your repo, and then press **Enter**. (You might receive a prompt to sign in to GitHub; if so, do so.) |
| 41 | + |
| 42 | + After Visual Studio clones your repo, Team Explorer closes and Solution Explorer opens. A message appears that says *Click on Solutions and Folders above to view a list of Solutions*. Choose **Solutions and Folders**. |
| 43 | + |
| 44 | +  |
| 45 | + |
| 46 | +1. If you have a solution file available, it will appear in the "Solutions and Folders" fly-out menu. Choose it, and Visual Studio opens your solution. |
| 47 | + |
| 48 | +  |
| 49 | + |
| 50 | + If you do not have a solution file (specifically, a .sln file) in your repo, the fly-out menu will say "No Solutions Found." However, you can double-click any file from the folder menu to open it in the Visual Studio code editor. |
| 51 | + |
| 52 | +### Review your work |
| 53 | + |
| 54 | +View the following animation to check the work that you completed in the previous section. |
| 55 | + |
| 56 | +  |
| 57 | + |
| 58 | +## Open a project from an Azure DevOps repo by using Visual Studio 2017 |
| 59 | + |
| 60 | +1. Open Visual Studio 2017. |
| 61 | + |
| 62 | +1. From the top menu bar, select **File** > **Open** > **Open from Source Control**. |
| 63 | + |
| 64 | + The **Team Explorer - Connect** pane opens. |
| 65 | + |
| 66 | +  |
| 67 | + |
| 68 | +1. Here are two ways to connect to your Azure DevOps repo: |
| 69 | + |
| 70 | + - In the **Hosted Service Providers** section, select **Connect...**. |
| 71 | + |
| 72 | +  |
| 73 | + |
| 74 | + - In the **Manage Connections** drop-down list, select **Connect to a Project...**. |
| 75 | + |
| 76 | +  |
| 77 | + |
| 78 | +1. In the **Connect to a Project** dialog box, choose the repo that you want to connect to, and then select **Clone**. |
| 79 | + |
| 80 | +  |
| 81 | + |
| 82 | + > [!NOTE] |
| 83 | + > What you see in the list box depends on the Azure DevOps repositories that you have access to. |
| 84 | +
|
| 85 | +1. After Visual Studio clones your repo, Team Explorer closes and Solution Explorer opens. A message appears that says *Click on Solutions and Folders above to view a list of Solutions*. Choose **Solutions and Folders**. |
| 86 | + |
| 87 | +  |
| 88 | + |
| 89 | + A solution file (specifically, a .sln file), will appear in the "Solutions and Folders" fly-out menu. Choose it, and Visual Studio opens your solution. |
| 90 | + |
| 91 | + If you do not have a solution file in your repo, the fly-out menu will say "No Solutions Found". However, you can double-click any file from the folder menu to open it in the Visual Studio code editor. |
| 92 | + |
| 93 | +## Next steps |
| 94 | + |
| 95 | +If you're ready to code with Visual Studio 2017, dive into any of the following language-specific tutorials: |
| 96 | + |
| 97 | +- [Visual Studio tutorials | **C#**](./csharp/index.yml) |
| 98 | +- [Visual Studio tutorials | **Visual Basic**](./visual-basic/index.yml) |
| 99 | +- [Visual Studio tutorials | **C++**](/cpp/get-started/tutorial-console-cpp) |
| 100 | +- [Visual Studio tutorials | **Python**](../python/index.yml) |
| 101 | +- [Visual Studio tutorials | **JavaScript**, **TypeScript**, and **Node.js**](../javascript/index.yml) |
| 102 | + |
| 103 | +## See also |
| 104 | + |
| 105 | +- [Azure DevOps Services: Get started with Azure Repos and Visual Studio](/azure/devops/repos/git/gitquickstart/) |
| 106 | +- [Microsoft Learn: Get started with Azure DevOps](/learn/modules/get-started-with-devops/) |
| 107 | +- [New Git experience in Visual Studio 2019](../ide/git-with-visual-studio.md?view=vs-2019&preserve-view=true) |
0 commit comments