Merge pull request #8615 from TerryGLee/tglee-fresh002

update 'Add > Reference' section for Dev16 & Dev17

Author: PRMerger10

docs/ide/how-to-add-or-remove-references-by-using-the-reference-manager.md

@@ -2,7 +2,7 @@
 title: Add references in the Reference Manager
 description: Learn how to use the Reference Manager dialog box to add and manage references to developed components.
 ms.custom: SEO-VS-2020
-ms.date: 08/02/2019
+ms.date: 08/30/2021
 ms.topic: how-to
 f1_keywords:
 - VS.ReferenceManager
@@ -44,18 +44,32 @@ The Reference Manager dialog box shows different categories on the left side, de
 - **Windows**, with **Core** and **Extensions** subgroups. You can explore the references in the Windows SDK or extension SDKs by using the **Object Browser**.
 
 - **Browse**, with **Recent** subgroup
- 
+
     > [!NOTE]
     > You might not see **Browse** in the Reference Manager dialog box if you're developing C++ projects.
 
 ## Add a reference
 
+::: moniker range="vs-2017"
+
 1. In **Solution Explorer**, right-click on the **References** or **Dependencies** node and choose **Add Reference**. You can also right-click on the project node and select **Add** > **Reference**.
 
    **Reference Manager** opens and lists the available references by group.
 
 2. Specify the references to add, and then select **OK**.
 
+::: moniker-end
+
+::: moniker range=">=vs-2019"
+
+1. In **Solution Explorer**, right-click on the **References** or **Dependencies** node and choose either **Add Project Reference**, **Add Shared Project Reference**, or **Add COM Reference**. (You can right-click the project node and select **Add** from the fly-out menu to choose from these options, too.)
+
+   **Reference Manager** opens and lists the available references by group.
+
+2. Specify the references to add, and then select **OK**.
+
+::: moniker-end
+
 ## Assemblies tab
 
 The **Assemblies** tab lists all .NET assemblies that are available for referencing. The **Assemblies** tab doesn't list any assemblies from the global assembly cache (GAC) because assemblies in the GAC are part of the run-time environment. If you deploy or copy an application that contains a reference to an assembly that's registered in the GAC, the assembly won't be deployed or copied with the application, regardless of the **Copy Local** setting. For more information, see [Manage references in a project](../ide/managing-references-in-a-project.md).