Merge pull request #7639 from TerryGLee/tglee-solproj

updates to Solutions & Projects topics

Author: PRMerger13

docs/get-started/tutorial-projects-solutions.md

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - multiple
 ---
-# Learn about projects and solutions
+# Introduction to projects and solutions
 
 In this introductory article, we'll explore what it means to create a *solution* and a *project* in Visual Studio. A solution is a container that's used to organize one or more related code projects, for example a class library project and a corresponding test project. We'll look at the properties of a project and some of the files it can contain. We'll also create a reference from one project to another.
 
@@ -44,11 +44,11 @@ We'll start our exploration by creating an empty solution. After you get to know
 
 1. Open Visual Studio.
 
-1. On the top menu bar, choose **File** > **New** > **Project**.
+1. On the top menu bar, select **File** > **New** > **Project**.
 
    The **New Project** dialog box opens.
 
-1. In the left pane, expand **Other Project Types**, then choose **Visual Studio Solutions**. In the center pane, choose the **Blank Solution** template. Name your solution **QuickSolution**, then choose the **OK** button.
+1. In the left pane, expand **Other Project Types**, then select **Visual Studio Solutions**. In the center pane, select the **Blank Solution** template. Name your solution **QuickSolution**, then select the **OK** button.
 
    ![Blank Solution template in Visual Studio 2017](media/tutorial-projects-new-solution.png "The Blank Solution template in Visual Studio 2017.")
 
@@ -60,16 +60,16 @@ We'll start our exploration by creating an empty solution. After you get to know
 
 1. Open Visual Studio.
 
-2. On the start window, choose **Create a new project**.
+2. On the start window, select **Create a new project**.
 
-3. On the **Create a new project** page, enter **blank solution** into the search box, select the **Blank Solution** template, and then choose **Next**.
+3. On the **Create a new project** page, enter **blank solution** into the search box, select the **Blank Solution** template, and then select **Next**.
 
    ![Blank Solution template in Visual Studio 2019](media/vs-2019/tutorial-projects-blank-solution-template.png "The Blank Solution template in Visual Studio 2019.")
 
     > [!TIP]
     > If you have several workloads installed, the **Blank Solution** template might not appear at the top of your list of search results. Try scrolling to the **Other results based on your search** section of the list. It should appear there.
 
-4. Name the solution **QuickSolution**, and then choose **Create**.
+4. Name the solution **QuickSolution**, and then select **Create**.
 
    A solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
 
@@ -81,39 +81,39 @@ Now let's add our first project to the solution. We'll start with an empty proje
 
 ::: moniker range="vs-2017"
 
-1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, choose **Add** > **New Project**.
+1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, select **Add** > **New Project**.
 
    The **Add New Project** dialog box opens.
 
-1. In the left pane, expand **Visual C#** and choose **Windows Desktop**. Then, in the middle pane, choose the **Empty Project (.NET Framework)** template. Name the project **QuickDate**, then choose **OK**.
+1. In the left pane, expand **Visual C#** and select **Windows Desktop**. Then, in the middle pane, select the **Empty Project (.NET Framework)** template. Name the project **QuickDate**, then select **OK**.
 
    A project named QuickDate appears beneath the solution in **Solution Explorer**. Currently it contains a single file called *App.config*.
 
    > [!NOTE]
-   > If you don't see **Visual C#** in the left pane of the dialog box, you must install the **.NET desktop development** Visual Studio workload. Visual Studio uses workload-based installation to install only the components you need for the type of development you do. An easy way to install a new workload is to choose the **Open Visual Studio Installer** link in the bottom left corner of the **Add New Project** dialog box. After Visual Studio Installer launches, choose the **.NET desktop development** workload and then the **Modify** button.
+   > If you don't see **Visual C#** in the left pane of the dialog box, you must install the **.NET desktop development** Visual Studio workload. Visual Studio uses workload-based installation to install only the components you need for the type of development you do. An easy way to install a new workload is to select the **Open Visual Studio Installer** link in the bottom left corner of the **Add New Project** dialog box. After Visual Studio Installer launches, select the **.NET desktop development** workload and then the **Modify** button.
    >
    > ![Open Visual Studio Installer link](media/tutorial-projects-open-installer.png "The Open Visual Studio Installer link in the Add New Project dialog in Visual Studio 2017.")
 
 ::: moniker-end
 
 ::: moniker range=">=vs-2019"
 
-1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, choose **Add** > **New Project**.
+1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, select **Add** > **New Project**.
 
    A dialog box opens that says **Add a new project**.
 
 1. Enter the text **empty** into the search box at the top, and then select **C#** under **Language**.
 
-1. Select the **Empty Project (.NET Framework)** template, and then choose **Next**.
+1. Select the **Empty Project (.NET Framework)** template, and then select **Next**.
 
-1. Name the project **QuickDate**, then choose **Create**.
+1. Name the project **QuickDate**, then select **Create**.
 
    A project named QuickDate appears beneath the solution in **Solution Explorer**. Currently it contains a single file called *App.config*.
 
    > [!NOTE]
    > If you don't see the **Empty Project (.NET Framework)** template, you must install the **.NET desktop development** Visual Studio workload. Visual Studio uses workload-based installation to install only the components you need for the type of development you do.
    >
-   >An easy way to install a new workload when you're creating a new project is to choose the **Install more tools and features** link under the text that says **Not finding what you're looking for?**. After Visual Studio Installer launches, choose the **.NET desktop development** workload and then the **Modify** button.
+   >An easy way to install a new workload when you're creating a new project is to select the **Install more tools and features** link under the text that says **Not finding what you're looking for?**. After Visual Studio Installer launches, select the **.NET desktop development** workload and then the **Modify** button.
    >
    > ![Open Visual Studio Installer link](media/vs-2019/tutorial-projects-open-installer.png "The Open Visual Studio Installer link in the Create a New Project dialog in Visual Studio.")
 
@@ -123,11 +123,11 @@ Now let's add our first project to the solution. We'll start with an empty proje
 
 We have an empty project. Let's add a code file.
 
-1. From the right-click or context menu of the **QuickDate** project in **Solution Explorer**, choose **Add** > **New Item**.
+1. From the right-click or context menu of the **QuickDate** project in **Solution Explorer**, select **Add** > **New Item**.
 
    The **Add New Item** dialog box opens.
 
-1. Expand **Visual C# Items**, then choose **Code**. In the middle pane, choose the **Class** item template. Name the class **Calendar**, and then choose the **Add** button.
+1. Expand **Visual C# Items**, then select **Code**. In the middle pane, select the **Class** item template. Name the class **Calendar**, and then select the **Add** button.
 
    A file named *Calendar.cs* is added to the project. The *.cs* on the end is the file extension that is given to C# code files. The file appears in the visual project hierarchy in **Solution Explorer**, and its contents are opened in the editor.
 
@@ -163,11 +163,11 @@ It is common for solutions to contain more than one project, and often these pro
 
 Let's add a unit test project to our solution. This time we'll start from a project template so we don't have to add an additional code file to the project.
 
-1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, choose **Add** > **New Project**.
+1. From the right-click or context menu of **Solution 'QuickSolution'** in **Solution Explorer**, select **Add** > **New Project**.
 
 ::: moniker range="vs-2017"
 
-2. In the left pane, expand **Visual C#** and choose the **Test** category. In the middle pane, choose the **MSTest Test Project (.NET Core)** project template. Name the project **QuickTest**, and then choose **OK**.
+2. In the left pane, expand **Visual C#** and select the **Test** category. In the middle pane, select the **MSTest Test Project (.NET Core)** project template. Name the project **QuickTest**, and then select **OK**.
 
    A second project is added to **Solution Explorer**, and a file named *UnitTest1.cs* opens in the editor.
 
@@ -179,9 +179,9 @@ Let's add a unit test project to our solution. This time we'll start from a proj
 
 2. In the **Add a new project** dialog box, enter the text **unit test** into the search box at the top, and then select **C#** under **Language**.
 
-3. Choose the **MSTest Test Project (.NET Core)** project template, and then choose **Next**.
+3. Select the **MSTest Test Project (.NET Core)** project template, and then select **Next**.
 
-4. Name the project **QuickTest**, and then choose **Create**.
+4. Name the project **QuickTest**, and then select **Create**.
 
    A second project is added to **Solution Explorer**, and a file named *UnitTest1.cs* opens in the editor.
 
@@ -195,30 +195,30 @@ We're going to use the new unit test project to test our method in the **QuickDa
 
 ::: moniker range="vs-2017"
 
-1. Choose the **Dependencies** node in the **QuickTest** project, and from the right-click or context menu, choose **Add Reference**.
+1. Select the **Dependencies** node in the **QuickTest** project, and from the right-click or context menu, select **Add Reference**.
 
    The **Reference Manager** dialog box opens.
 
-1. In the left pane, expand **Projects** and choose **Solution**. In the middle pane, choose the checkbox next to **QuickDate**, and then choose **OK**.
+1. In the left pane, expand **Projects** and select **Solution**. In the middle pane, select the checkbox next to **QuickDate**, and then select **OK**.
 
    A reference to the **QuickDate** project is added.
 
-   ![Visual Studio 2019 Solution Explorer showing project reference](media/vs-2019/tutorial-projects-solution-explorer-reference.png "Solution Explorer showing a project reference in Visual Studio.")
+   ![A screenshot of Solution Explorer showing project reference in Visual Studio](media/vs-2019/tutorial-projects-solution-explorer-reference.png "A screenshot of Solution Explorer showing a project reference in Visual Studio.")
 
 ::: moniker-end
 
 ::: moniker range="vs-2019"
 
-1. Choose the **Dependencies** node in the **QuickTest** project, and from the right-click or context menu, choose **Add Project Reference...**.
+1. Select the **Dependencies** node in the **QuickTest** project, and from the right-click or context menu, select **Add Project Reference...**.
 
    The **Reference Manager** dialog box opens.
 
-1. In the left pane, expand **Projects** and choose **Solution**. In the middle pane, choose the checkbox next to **QuickDate**, and then choose **OK**.
+1. In the left pane, expand **Projects**, and then select **Solution**. In the middle pane, select the checkbox next to **QuickDate**, and then select **OK**.
 
    A reference to the **QuickDate** project is added.
 
-   ![Visual Studio 2019 Solution Explorer showing project reference](media/vs-2019/tutorial-projects-solution-explorer-reference.png)
-   
+   ![A screenshot of Solution Explorer showing a project reference in Visual Studio 2019](media/vs-2019/tutorial-projects-solution-explorer-reference.png)
+
 ::: moniker-end
 
 ## Add test code
@@ -271,7 +271,7 @@ The line in the *Calendar.cs* file that contains the <xref:System.Runtime.Compil
 
 ## Next steps
 
-If you want to check that your unit test is working, choose **Test** > **Run** > **All Tests** from the menu bar. A window called **Test Explorer** opens, and you should see that the **TestGetCurrentDate** test passes.
+If you want to check that your unit test is working, select **Test** > **Run** > **All Tests** from the menu bar. A window called **Test Explorer** opens, and you should see that the **TestGetCurrentDate** test passes.
 
 ![Test Explorer in Visual Studio showing passed test](media/tutorial-projects-test-explorer.png "Test Explorer in Visual Studio showing a passed test.")
 
@@ -291,7 +291,7 @@ If you want to check that your unit test is working, choose **Test** > **Run** >
 
 ## See also
 
-- [Create projects and solutions](../ide/creating-solutions-and-projects.md)
+- [Work with projects and solutions](../ide/creating-solutions-and-projects.md)
 - [Manage project and solution properties](../ide/managing-project-and-solution-properties.md)
 - [Manage references in a project](../ide/managing-references-in-a-project.md)
 - [Develop code in Visual Studio without projects or solutions](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md)

docs/ide/create-new-project.md

@@ -97,4 +97,4 @@ If you want to add an additional project to a solution, right-click the solution
 
 ## See also
 
-- [Create solutions and projects](creating-solutions-and-projects.md)
+- [Work with solutions and projects](creating-solutions-and-projects.md)

docs/ide/how-to-set-multiple-startup-projects.md

@@ -31,5 +31,5 @@ Visual Studio allows you to specify how more than one project is run when you st
 ## See also
 
 - [Compile and build](../ide/compiling-and-building-in-visual-studio.md)
-- [Create solutions and projects](../ide/creating-solutions-and-projects.md)
+- [Work with solutions and projects](../ide/creating-solutions-and-projects.md)
 - [Manage project and solution properties](../ide/managing-project-and-solution-properties.md)

docs/ide/solutions-and-projects-in-visual-studio.md

@@ -1,5 +1,5 @@
 ---
-title: Solutions and projects overview
+title: Learn about solutions and projects
 description: Learn about Visual Studio projects and solutions, how to create new projects from a template, and how to view & manage projects in Solution Explorer.
 ms.custom: SEO-VS-2020
 ms.date: 12/15/2020
@@ -45,7 +45,7 @@ Project files are based on the [MSBuild XML schema](../msbuild/msbuild-project-f
 
 ## Solutions
 
-A project is contained within a *solution*. Despite its name, a solution is not an "answer". It's simply a container for one or more related projects, along with build information, Visual Studio window settings, and any miscellaneous files that aren't associated with a particular project. A solution is described by a text file (extension *.sln*) with its own unique format; it's not intended to be edited by hand.
+A project is contained within a *solution*. Despite its name, a solution is not an "answer". It's simply a container for one or more related projects, along with build information, Visual Studio window settings, and any miscellaneous files that aren't associated with a particular project.
 
 ### Solution file
 
@@ -56,6 +56,9 @@ Visual Studio uses two file types (*.sln* and *.suo*) to store settings for solu
 |.sln|Visual Studio Solution|Organizes projects, project items, and solution items in the solution.|
 |.suo|Solution User Options|Stores user-level settings and customizations, such as breakpoints.|
 
+> [!IMPORTANT]
+> A solution is described by a text file (extension *.sln*) with its own unique format; it's not intended to be edited by hand. Conversely, the *.suo* file is a hidden file that is not displayed under the default File Explorer settings. To show hidden files, on the **View** menu in File Explorer, select the **Hidden Items** checkbox.
+
 ### Solution folder
 
 A "solution folder" is a virtual folder that's only in **Solution Explorer**, where you can use it to group projects in a solution. If you want to locate a solution file on a computer, go to **Tools** > **Options** > **Projects and Solutions** > **Locations**. For more information, see [Options dialog box: Projects and Solutions > Locations](./reference/projects-solutions-locations-options.md).