Merge pull request #1785 from gewarren/gewarren-add-reference

Fix add reference topics

Author: ktoliver

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

@@ -1,13 +1,8 @@
 ---
-title: "How to: Add or Remove References By Using the Reference Manager | Microsoft Docs"
-ms.custom: ""
-ms.date: "01/18/2018"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology:
-  - "vs-ide-general"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+title: Add References in the Reference Manager
+ms.date: 04/11/2018
+ms.technology: vs-ide-general
+ms.topic: conceptual
 f1_keywords:
   - "VS.ReferenceManager"
 helpviewer_keywords:
@@ -24,11 +19,11 @@ helpviewer_keywords:
   - "referencing components, assemblies not listed"
 author: "gewarren"
 ms.author: "gewarren"
-manager: ghogen
+manager: douge
 ms.workload:
   - "multiple"
 ---
-# How to: add or remove references by using the Reference Manager
+# How to: Add or remove references by using the Reference Manager
 
 You can use the **Reference Manager** dialog box to add and manage references to components that you, Microsoft, or another company developed. If you're developing a Universal Windows app, your project automatically references all of the correct Windows SDK DLLs. If you are developing a .NET application, your project automatically references mscorlib.dll. Some .NET APIs are exposed in components that you have to add manually. References to COM components or custom components have to be added manually.
 
@@ -46,16 +41,16 @@ The **Reference Manager** dialog box shows different categories on the left side
 
 - Browse, with the Recent subgroup.
 
-## Adding and removing a reference
+## Add and remove a reference
 
 ### To add a reference
 
-1. In **Solution Explorer**, right-click on the References node and choose **Add Reference**.
-
-2. Specify the references to add, and then choose the **OK** button.
+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**.
+
 ## Assemblies tab
 
 The **Assemblies** tab lists all .NET Framework 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 [Managing references in a project](../ide/managing-references-in-a-project.md).
@@ -134,15 +129,9 @@ Some components in the list may not be shown, depending on the .NET Framework ve
 
    Open the **Add Reference** dialog box again. The assemblies should appear on the **.NET** tab. If they do not, make sure that the assemblies are located in the specified *AssemblyLocation* directory, restart Visual Studio, and try again.
 
-## COM tab
-
-The COM tab lists all COM components that are available for referencing. If you want to add a reference to a registered COM DLL that contains an internal manifest, unregister the DLL first. Otherwise, Visual Studio adds the assembly reference as an ActiveX Control instead of as a native DLL.
-
-If a project type doesn't support COM, the tab won't appear in the **Reference Manager** dialog box.
+## Projects tab
 
-## Solution tab
-
-The Solution tab lists all compatible projects within the current solution, in the Projects sub-tab.
+The **Projects** tab lists all compatible projects within the current solution, in the **Solution** sub-tab.
 
 A project can reference another project that targets a different version of the .NET Framework. For example, you could create a project that targets the [!INCLUDE[net_v40_short](../code-quality/includes/net_v40_short_md.md)] but that references an assembly that's been built for the .NET Framework 2. However, the .NET Framework 2 project can't reference a [!INCLUDE[net_v40_short](../code-quality/includes/net_v40_short_md.md)] project. For more information, see [Multi-targeting overview](../ide/visual-studio-multi-targeting-overview.md).
 
@@ -191,6 +180,12 @@ An SDK is a collection of files that Visual Studio treats as a single component.
 
 If a project type doesn't support **Extensions**, the tab doesn't appear in the **Reference Manager** dialog box.
 
+## COM tab
+
+The COM tab lists all COM components that are available for referencing. If you want to add a reference to a registered COM DLL that contains an internal manifest, unregister the DLL first. Otherwise, Visual Studio adds the assembly reference as an ActiveX Control instead of as a native DLL.
+
+If a project type doesn't support COM, the tab doesn't appear in the **Reference Manager** dialog box.
+
 ## Browse button
 
 You can use the **Browse** button to browse for a component in the file system.
@@ -226,4 +221,4 @@ The search bar in the **Reference Manager** dialog box operates over the tab tha
 
 ## See also
 
-[Managing references in a project](../ide/managing-references-in-a-project.md)
+- [Manage references in a project](../ide/managing-references-in-a-project.md)

docs/ide/managing-references-in-a-project.md

@@ -1,13 +1,8 @@
 ---
-title: "Managing references in a project | Microsoft Docs"
-ms.custom: ""
-ms.date: "10/26/2017"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology:
-  - "vs-ide-general"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+title: Managing references in a project
+ms.date: 04/11/2018
+ms.technology: vs-ide-general
+ms.topic: conceptual
 f1_keywords:
   - "vs.ProjectPropertiesReferencePaths"
   - "cs.ProjectPropertiesReferencePaths"
@@ -24,19 +19,19 @@ helpviewer_keywords:
   - "objects [Visual Studio], referencing"
 author: "gewarren"
 ms.author: "gewarren"
-manager: ghogen
+manager: douge
 ms.workload:
   - "multiple"
 ---
-# Managing references in a project
+# Manage references in a project
 
 Before you write code against an external component or connected service, your project must first contain a reference to it. A reference is essentially an entry in a project file that contains the information that Visual Studio needs to locate the component or the service.
 
-To add a reference, right click on the References node in Solution Explorer and choose **Add Reference**. For more information, see [How to: Add or Remove References By Using the Reference Manager](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md).
+To add a reference, right click on the **References** or **Dependencies** node in **Solution Explorer** and choose **Add Reference**. You can also right-click on the project node and select **Add** > **Reference**. For more information, see [How to: Add or Remove References](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md).
 
-![Add a reference in Visual C++](../ide/media/vs2015_cpp_add_reference.png "vs2015_cpp_add_reference")
+![Add a reference in Visual C++](../ide/media/vs2015_cpp_add_reference.png)
 
-You can make a reference to the following types of components and services:
+You can add a reference to the following types of components and services:
 
 - .NET Framework class libraries or assemblies
 
@@ -76,11 +71,11 @@ If you determine that the Extension SDK being referenced by your app is not supp
 
 1. Restart Visual Studio and open your app.
 
-1. Right-click on the **References** node in the project that caused the error and choose **Add Reference**.
+1. Right-click on the **References** or **Dependencies** node in the project that caused the error and choose **Add Reference**.
 
 1. Click the **Windows** tab and then the **Extensions** sub-tab, then uncheck the checkboxes for the old Extension SDKs, and check the checkboxes for the new Extension SDKs. Click **OK**.
 
-## Adding a reference at design time
+## Add a reference at design time
 
 When you make a reference to an assembly in your project, Visual Studio searches for the assembly in the following locations:
 
@@ -89,7 +84,9 @@ When you make a reference to an assembly in your project, Visual Studio searches
 - Other project directories in the same solution. (You can find these assemblies on the **Projects** tab.)
 
 > [!NOTE]
-> All projects contain an implied reference to mscorlib. Visual Basic projects contain an implied reference to `Microsoft.VisualBasic`. All projects contain an implied reference to `System.Core`, even if `System.Core` is removed from the list of references.
+> - All projects contain an implied reference to mscorlib.
+> - All projects contain an implied reference to `System.Core`, even if `System.Core` is removed from the list of references.
+> - Visual Basic projects contain an implied reference to `Microsoft.VisualBasic`.
 
 ## References to shared components at run time
 
@@ -99,9 +96,9 @@ If you deploy an application that contains a reference to a custom component tha
 
 By default, the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property is set to **False** if the assembly or component is in the global assembly cache or is a framework component. Otherwise, the value is set to **True**. Project-to-project references are always set to **True**.
 
-## Referencing a project or assembly that targets a different version of the .NET Framework
+## Reference a project or assembly that targets a different version of the .NET Framework
 
-You can create applications that reference projects or assemblies that target a different version of the .NET Framework. For example, you could create an application that targets the [!INCLUDE[net_client_v40_long](../deployment/includes/net_client_v40_long_md.md)], that references an assembly that targets [!INCLUDE[dnprdnext](../ide/includes/dnprdnext_md.md)]. If you create a project that targets an earlier version of the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)], you cannot set a reference in that project to a project or assembly that targets a newer version.
+You can create applications that reference projects or assemblies that target a different version of the .NET Framework. For example, you could create an application that targets .NET Framework 4.6, that references an assembly that targets .NET Framework 4.5. If you create a project that targets an earlier version of the .NET Framework, you cannot set a reference in that project to a project or assembly that targets a newer version.
 
 For more information, see [Multi-targeting overview](../ide/visual-studio-multi-targeting-overview.md).
 
@@ -120,5 +117,5 @@ File references are direct references to assemblies outside the context of a Vis
 
 ## See also
 
-[Troubleshooting Broken References](../ide/troubleshooting-broken-references.md)
-[How to: Add or Remove References By Using the Reference Manager](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md)
+- [Troubleshooting broken references](../ide/troubleshooting-broken-references.md)
+- [How to: Add or remove references](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md)