Merge pull request #1540 from MicrosoftDocs/release-15.6

Merge release-15.6 to master

Author: gewarren

docs/ide/creating-solutions-and-projects.md

@@ -1,7 +1,7 @@
 ---
 title: "Create solutions and projects in Visual Studio | Microsoft Docs"
 ms.custom: ""
-ms.date: "06/16/2017"
+ms.date: 02/06/2018
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: "vs-ide-general"
@@ -13,7 +13,6 @@ f1_keywords:
   - "VS.ToolsOptionsPages.Projects.General"
   - "SolutionItemsProject"
 helpviewer_keywords: 
-  - "solutions [Visual Studio], deleting"
   - "solutions [Visual Studio], creating"
   - "projects [Visual Studio], creating"
 author: "gewarren"
@@ -41,7 +40,7 @@ That being said, solutions and projects are not required to develop apps in Visu
 
 ## To create a project from a project template
 
-1. There are multiple ways to create a new project in Visual Studio. On the Start Page, enter the name of a project template in the **Search project templates** box, or choose the **Create new project** link to open the **New Project** dialog box. You can also choose **File**, **New**, **Project...** on the menu bar, or choose the **New Project** button on the toolbar.
+1. There are multiple ways to create a new project in Visual Studio. On the Start Page, enter the name of a project template in the **Search project templates** box, or choose the **Create new project** link to open the **New Project** dialog box. You can also choose **File** > **New** > **Project...** on the menu bar, or choose the **New Project** button on the toolbar.
 
   ![Start page](./media/vside-newproject1.png)
 
@@ -54,23 +53,23 @@ That being said, solutions and projects are not required to develop apps in Visu
 
 1. Show the list of templates for the programming language you want to use by choosing the triangle next to the language name, and then choose a project type.
 
-  The following example shows the project templates available for Visual C# web projects.
+  The following example shows the project templates available for Visual C# .NET Core projects.
 
-  ![Project templates](./media/vside-newproject-projects-list.png)
+  ![Project templates](./media/new-project-dialog-net-core.png)
 
 1. Enter a name for the new project in the **Name** box. You can choose to save the project in the default location on your system, or choose the **Browse** button to find another location.
 
   You can also optionally choose to change the solution name, or add the new project to a Git repository by choosing **Add to Source Control**.
 
 1. Choose the **OK** button to create the solution and project.
 
-1. If you want to add an additional project to the solution, choose the solution node in Solution Explorer, and then on the menu bar, choose **Project**, **Add New Item**.
+1. If you want to add an additional project to the solution, choose the solution node in Solution Explorer, and then on the menu bar, choose **Project** > **Add New Item**.
 
 ## Create a project from existing code files
 
 If you have a collection of code source files, you can easily add them to a project.
 
-1. On the menu, choose **File**, **New**, **Project From Existing Code**.
+1. On the menu, choose **File** > **New** > **Project From Existing Code**.
 
 1. In the **Create Project from Existing Code Files** wizard, choose the project type you want in the **What type of project would you like to create?** drop-down list box, and then choose the **Next** button.
 
@@ -81,31 +80,26 @@ If you have a collection of code source files, you can easily add them to a proj
 
 ## Add files to a solution
 
-If you have a file that applies to multiple projects, such as a readme file for the solution, or other files that logically belong at the solution level rather than under a specific project, then you can add them to the solution itself. To add an item to a solution, on the context (right-click) menu of the solution node in **Solution Explorer**, choose **Add**, **New Item**, or **Add**, **Existing Item**.
+If you have a file that applies to multiple projects, such as a readme file for the solution, or other files that logically belong at the solution level rather than under a specific project, then you can add them to the solution itself. To add an item to a solution, on the context (right-click) menu of the solution node in **Solution Explorer**, choose **Add** > **New Item**, or **Add** > **Existing Item**.
 
 ## Create a .NET project that targets a specific version of the .NET Framework
 
-When you create a project, you can specify a specific version of the .NET Framework that you want the project to use. To specify a .NET framework version, choose the **.NET Framework** version drop-down menu in the **New Project** dialog box.
+When you create a project, you can specify a specific version of the .NET Framework that you want the project to use. To specify a .NET framework version, choose the **Framework** drop-down menu in the **New Project** dialog box.
 
-![.NET Framework version selector](./media/vside-newproject-framework.png)
+![Framework drop-down in New Project dialog](./media/vside-newproject-framework.png)
 
 > [!NOTE]
-> If you are creating a project from a .NET Core template, the .NET Framework version you select in the drop-down is ignored.
-
-> [!TIP]
-> If you set the .NET Framework version before selecting a project template, then Visual Studio will only show templates that are compatible with that .NET Framework version.
-
-You must have .NET Framework 3.5 installed on your system to access .NET Framework versions earlier than .NET Framework 4.
+> You must have .NET Framework 3.5 installed on your system to access .NET Framework versions earlier than .NET Framework 4.
 
 ## Create empty solutions
 
 You can also create empty solutions that have no projects. This might be preferable in cases where you want to construct your solution and projects from scratch.
 
 ### To create an empty solution
 
-1. On the menu, choose **File**, **New**, **Project...**.
+1. On the menu, choose **File** > **New** > **Project...**.
 
-1. In the left (**Templates**) pane, choose **Other Project Types**, **Visual Studio Solutions** in the expanded list.
+1. In the left (**Templates**) pane, choose **Other Project Types** > **Visual Studio Solutions** in the expanded list.
 
 1. In the middle pane, choose **Blank Solution**.
 
@@ -119,7 +113,7 @@ As mentioned earlier, you can also open code files without needing a project or
 
 If you create a .NET-based project without specifying a disk location, it is a temporary project. Temporary projects enable you to experiment with .NET projects. At any time while you are working with a temporary project, you can choose to save it or discard it.
 
-To create a temporary project, first go to **Tools**, **Options**, **Projects and Solutions**, **General**, and uncheck the **Save new projects when created** checkbox. Then open the **New Project** dialog box as usual.
+To create a temporary project, first go to **Tools** > **Options** > **Projects and Solutions** > **General**, and uncheck the **Save new projects when created** checkbox. Then open the **New Project** dialog box as usual.
 
 ## Delete a solution, project, or item
 
@@ -138,7 +132,7 @@ You can delete solutions and their contents permanently, but not by using the Vi
 
 ## See also
 
-[Solutions and Projects](../ide/solutions-and-projects-in-visual-studio.md)  
+[Solutions and projects](../ide/solutions-and-projects-in-visual-studio.md)  
 [Microsoft's open source repositories on GitHub](https://github.com/Microsoft)  
 [Visual Studio Samples](../ide/visual-studio-samples.md)  
-[Developer code samples](https://code.msdn.microsoft.com/)  
+[Developer code samples](https://code.msdn.microsoft.com/)

docs/ide/editorconfig-code-style-settings-reference.md

@@ -386,8 +386,8 @@ The following table shows the rule names, rule IDs, applicable programming langu
 | dotnet_style_explicit_tuple_names | IDE0033 | C# 7.0+ and Visual Basic 15+ | true:suggestion | First release |
 | dotnet_style_coalesce_expression | IDE0029 | C# and Visual Basic | true:suggestion | First release |
 | dotnet_style_null_propagation | IDE0031 | C# 6.0+ and Visual Basic 14+ | true:suggestion | First release |
-| dotnet_prefer_inferred_tuple_names | IDE0037 | C# 7.1+ and Visual Basic 15+ | true:suggestion | 15.6 preview 2 |
-| dotnet_prefer_inferred_anonymous_type_member_names | IDE0037 | C# and Visual Basic | true:suggestion | 15.6 preview 2 |
+| dotnet_prefer_inferred_tuple_names | IDE0037 | C# 7.1+ and Visual Basic 15+ | true:suggestion | 15.6 |
+| dotnet_prefer_inferred_anonymous_type_member_names | IDE0037 | C# and Visual Basic | true:suggestion | 15.6 |
 
 **dotnet\_style\_object_initializer**
 

docs/ide/finding-and-using-visual-studio-extensions.md

@@ -68,7 +68,7 @@ If you wish to disable automatic updates, you can disable the feature for all ex
 
 New in **Visual Studio 2017 version 15.3**, Visual Studio notifies you if it suspects that an extension was involved in a crash during a previous session. When Visual Studio crashes, it stores the exception stack. The next time Visual Studio launches, it examines the stack, starting with the leaf and working towards the base. If Visual Studio determines that a frame belongs to a module that is part of an installed and enabled extension, it shows a notification.
 
-New in **Visual Studio 2017 version 15.6 preview 3**, Visual Studio also notifies you if it suspects an extension is causing the UI to be unresponsive.
+New in **Visual Studio 2017 version 15.6**, Visual Studio also notifies you if it suspects an extension is causing the UI to be unresponsive.
 
 When these notifications are shown, you can ignore the notification or take one of the following actions:
 

docs/ide/go-to-and-peek-definition.md

@@ -16,7 +16,7 @@ helpviewer_keywords:
 author: "gewarren"
 ms.author: "gewarren"
 manager: ghogen
-ms.workload: 
+ms.workload:
   - "multiple"
 ---
 # View type and member definitions
@@ -66,7 +66,7 @@ For example, if you run the **Go To Definition** command for <xref:System.Consol
 
 ### View decompiled source definitions instead of metadata (C#)
 
-New in **Visual Studio 2017 version 15.6 preview 2**, you can set an option to see decompiled source code when you view the definition of a C# type or member who's source code is unavailable. To turn on this feature, choose **Tools** > **Options** from the menu bar. Then, expand **Text Editor** > **C#** > **Advanced**, and select **Enable navigation to decompiled sources**.
+New in **Visual Studio 2017 version 15.6**, you can set an option to see decompiled source code when you view the definition of a C# type or member who's source code is unavailable. To turn on this feature, choose **Tools** > **Options** from the menu bar. Then, expand **Text Editor** > **C#** > **Advanced**, and select **Enable navigation to decompiled sources**.
 
 ![Viewing a decompiled definition](media/go-to-definition-decompiled-sources.png)
 
@@ -75,5 +75,5 @@ New in **Visual Studio 2017 version 15.6 preview 2**, you can set an option to s
 
 ## See also
 
-[Navigating Code](../ide/navigating-code.md)  
+[Navigating Code](../ide/navigating-code.md)
 [How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md)

docs/ide/how-to-target-a-version-of-the-dotnet-framework.md

@@ -1,65 +1,64 @@
 ---
-title: "How to: Target a Version of the .NET Framework | Microsoft Docs"
+title: "Target a .NET Framework version in Visual Studio | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/08/2017"
+ms.date: 02/06/2018
 ms.reviewer: ""
 ms.suite: ""
-ms.technology: 
-  - "vs-ide-general"
+ms.technology: vs-ide-general
 ms.tgt_pltfrm: ""
 ms.topic: "article"
 helpviewer_keywords: 
-  - "targeting .NET Framework version [Visual Studio]"
-  - "versions [Visual Studio], targeting .NET Framework version"
+  - "targeting .NET Framework [Visual Studio]"
+  - ".NET Framework version [Visual Studio]"
 author: "gewarren"
 ms.author: "gewarren"
 manager: ghogen
 ms.workload: 
   - "dotnet"
 ---
-# How to: Target a Version of the .NET Framework
+# How to: Target a version of the .NET Framework
 
 This document describes how to target a version of the .NET Framework when you create a project, and how to change the targeted version in an existing Visual Basic, C#, or Visual F# project.
 
 > [!IMPORTANT]
 > For information about how to change the target version for C++ projects, see [How to: Modify the Target Framework and Platform Toolset](/cpp/build/how-to-modify-the-target-framework-and-platform-toolset).
 
-## Targeting a version when you create a project
+## To target a version when you create a project
 
-When you create a project, the version of the .NET Framework that you target determines which templates you can use.
+When you create a project, the available .NET Framework versions depend on which versions are installed, and the selected template in the **New Project** dialog box.
 
-### To target a version when you create a project
+1. On the menu bar, choose **File** > **New** > **Project...**.
 
-1.  On the menu bar, choose **File**, **New**, **Project**.
+1. In the list of installed templates, choose the type of project that you want to create, and enter a name for the project.
 
-2.  In the list at the top of the **New Project** dialog box, choose the version of the .NET Framework that you want your project to target.
+1. From the **Framework** drop-down list at the bottom of the **New Project** dialog box, choose the version of the .NET Framework that you want your project to target.
 
-3.  In the list of installed templates, choose the type of project that you want to create, name the project, and then choose the **OK** button.
+    The list of frameworks shows only those versions that are applicable to the template that you chose. Some project types, such as .NET Core, do not require .NET Framework. In such instances, the **Framework** drop-down list is hidden.
 
-    The list of templates shows only those projects that are supported by the version of the .NET Framework that you chose.
+    ![Framework drop-down in New Project dialog](media/vside-newproject-framework.png)
 
-## Changing the target version
+1. Choose the **OK** button.
+
+## To change the targeted version
 
 You can change the targeted version of the .NET Framework in a Visual Basic, C#, or Visual F# project by following this procedure.
 
 For information about how to change the target version for C++ projects, see [How to: Modify the Target Framework and Platform Toolset](/cpp/build/how-to-modify-the-target-framework-and-platform-toolset).
 
-### To change the targeted version
-
-1.  In **Solution Explorer**, open the shortcut menu for the project that you want to change, and then choose **Properties**.
+1. In **Solution Explorer**, open the shortcut menu for the project that you want to change, and then choose **Properties**.
 
     ![Visual Studio Solution Explorer Properties](../ide/media/vs_slnexplorer_properties.png "vs_slnExplorer_Properties")
 
-2. In the left column of the properties window, choose the **Application** tab.
+1. In the left column of the properties window, choose the **Application** tab.
 
     ![Visual Studio App Properties Application tab](../ide/media/vs_slnexplorer_properties_applicationtab.png "vs_slnExplorer_Properties_ApplicationTab")
 
     > [!NOTE]
     > After you create a UWP app, you can't change the targeted version of either Windows or the .NET Framework.
 
-3.  In the **Target Framework** list, choose the version that you want.
+1. In the **Target Framework** list, choose the version that you want.
 
-4.  In the verification dialog box that appears, choose the **Yes** button.
+1. In the verification dialog box that appears, choose the **Yes** button.
 
     The project unloads. When it reloads, it targets the .NET Framework version that you just chose.
 

docs/ide/media/new-project-dialog-net-core.png

@@ -23,7 +23,7 @@ For information about common keyboard shortcuts, see [Keyboard tips](../ide/tips
 
 Write code more quickly by using the following features.
 
-- **Use convenience commands**. Visual Studio contains various commands to help you accomplish common editing tasks faster. For example, in **Visual Studio 2017 version 15.6 preview 2** and later, you can choose a command to easily duplicate a line of code without having to copy it, reposition the cursor, and then paste it. Choose **Edit** > **Duplicate** or press **Ctrl**+**E**,**V**. You can also quickly expand or contract a selection of text by choosing **Edit** > **Advanced** > **Expand Selection** or **Edit** > **Advanced** > **Contract Selection**, or by pressing **Shift**+**Alt**+**=** or **Shift**+**Alt**+**-**  (available in **Visual Studio 2017 version 15.5** and later).
+- **Use convenience commands**. Visual Studio contains various commands to help you accomplish common editing tasks faster. For example, in **Visual Studio 2017 version 15.6** and later, you can choose a command to easily duplicate a line of code without having to copy it, reposition the cursor, and then paste it. Choose **Edit** > **Duplicate** or press **Ctrl**+**E**,**V**. You can also quickly expand or contract a selection of text by choosing **Edit** > **Advanced** > **Expand Selection** or **Edit** > **Advanced** > **Contract Selection**, or by pressing **Shift**+**Alt**+**=** or **Shift**+**Alt**+**-**  (available in **Visual Studio 2017 version 15.5** and later).
 
 - **Use IntelliSense**. As you enter code in the editor, IntelliSense information, such as List Members, Parameter Info, Quick Info, Signature Help, and Complete Word, appears. These features support fuzzy matching of text; for example, the results lists for List Members includes not only entries that start with the characters that you have entered but also entries that contain the character combination anywhere in their names. For more information, see [Using IntelliSense](../ide/using-intellisense.md).
 

docs/ide/media/vside-newproject-framework.png

@@ -1,11 +1,7 @@
 ---
 title: "Visual Studio keyboard shortcuts | Microsoft Docs"
-ms.custom: ""
 ms.date: "06/21/2017"
-ms.reviewer: ""
-ms.suite: ""
 ms.technology: vs-ide-general
-ms.tgt_pltfrm: ""
 ms.topic: "article"
 author: "gewarren"
 ms.author: "gewarren"
@@ -15,7 +11,11 @@ ms.workload:
 ---
 # Keyboard tips for Visual Studio
 
-You can navigate in Visual Studio more easily by using the keyboard shortcuts in this topic. This topic is only a subset of the available keyboard shortcuts. For a more complete list, see [Default Keyboard Shortcuts in Visual Studio](../ide/default-keyboard-shortcuts-in-visual-studio.md). For information about how to optimize Visual Studio for accessibility, see [Accessibility Tips and Tricks](../ide/reference/accessibility-tips-and-tricks.md).
+You can navigate in Visual Studio more easily by using the keyboard shortcuts in this article.
+
+The shortcuts listed here are only a subset of the available keyboard shortcuts. For a more complete list, see [Default Keyboard Shortcuts in Visual Studio](../ide/default-keyboard-shortcuts-in-visual-studio.md).
+
+For information about how to optimize Visual Studio for accessibility, see [Accessibility Tips and Tricks](../ide/reference/accessibility-tips-and-tricks.md).
 
 ## Window management
 
@@ -78,7 +78,7 @@ You can navigate in Visual Studio more easily by using the keyboard shortcuts in
 |Editor Zoom|Ctrl+Shift+> (In), Ctrl+Shift+< (Out)||
 |Block Selection|Hold Alt and drag mouse, Shift+Alt+Arrow Keys||
 |Move Line Up/Down|Alt+Up / Alt+Down||
-|Duplicate line|Ctrl+E,V|Visual Studio 2017 version 15.6 preview 2|
+|Duplicate line|Ctrl+E,V|Visual Studio 2017 version 15.6|
 |Expand selection|**Shift**+**Alt**+**=**|Visual Studio 2017 version 15.5|
 |Contract selection|**Shift**+**Alt**+**-**|Visual Studio 2017 version 15.5|
 |Go To Definition|F12||