Merge pull request #3912 from MicrosoftDocs/master637038398118798027

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: gewarren

docs/ide/step-11-run-your-program-and-try-other-features.md

@@ -1,6 +1,6 @@
 ---
-title: "Step 11: Run your app and try other features"
-ms.date: 08/30/2019
+title: "Step 11: Run your picture viewer app and try other features"
+ms.date: 09/11/2019
 ms.assetid: 656614d0-4fe7-4a67-8edc-c10919377d09
 ms.topic: tutorial
 ms.prod: visual-studio-windows
@@ -14,9 +14,9 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Step 11: Run your app and try other features
+# Step 11: Run your picture viewer app and try other features
 
-Your app is finished and ready to run. You can run your app and set the background color of the <xref:System.Windows.Forms.PictureBox>. To learn more, try to improve the application by changing the color of the form, customizing the buttons and check box, and changing the properties of the form.
+Your picture viewer app is finished and ready to run. You can run your app and set the background color of the <xref:System.Windows.Forms.PictureBox>. To learn more, try to improve the application by changing the color of the form, customizing the buttons and check box, and changing the properties of the form.
 
 ## How to run your app and set the background color
 

docs/ide/step-3-set-your-form-properties.md

@@ -71,7 +71,7 @@ Next, you use the **Properties** window to change the way your form looks.
 
 * To go to the next tutorial step, see **[Step 4: Lay out your form with a TableLayoutPanel control](../ide/step-4-lay-out-your-form-with-a-tablelayoutpanel-control.md)**.
 
-* To return to the previous tutorial step, see [Step 2: Run your picture viewer app(../ide/step-2-run-your-program.md).
+* To return to the previous tutorial step, see [Step 2: Run your picture viewer app](../ide/step-2-run-your-program.md).
 
 ## See also
 

docs/ide/step-5-add-controls-to-your-form.md

@@ -79,7 +79,7 @@ In this step, you add controls, such as a <xref:System.Windows.Forms.PictureBox>
 
 ## To continue or review
 
-* To go to the next tutorial step, see [Step 6: Name your button controls](../ide/step-6-name-your-button-controls.md).
+* To go to the next tutorial step, see **[Step 6: Name your button controls](../ide/step-6-name-your-button-controls.md)**.
 
 * To return to the previous tutorial step, see [Step 4: Lay out your form with a TableLayoutPanel control](../ide/step-4-lay-out-your-form-with-a-tablelayoutpanel-control.md).
 

docs/ide/tutorial-1-create-a-picture-viewer.md

@@ -45,7 +45,7 @@ When you finish, your app should look similar to the following image:
 
 |Title|Description|
 |-----------|-----------------|
-|[Step 1: Create a Windows Forms application project](../ide/step-1-create-a-windows-forms-application-project.md)|Begin by creating a Windows Forms App project.|
+|[Step 1: Create a Windows Forms App project](../ide/step-1-create-a-windows-forms-application-project.md)|Begin by creating a Windows Forms App project.|
 |[Step 2: Run your picture viewer app](../ide/step-2-run-your-program.md)|Run the Windows Forms App project that you created in the previous step.|
 |[Step 3: Set your form properties](../ide/step-3-set-your-form-properties.md)|Change the way your form looks using the **Properties** window.|
 |[Step 4: Lay out your form with a TableLayoutPanel control](../ide/step-4-lay-out-your-form-with-a-tablelayoutpanel-control.md)|Add a `TableLayoutPanel` control to your form.|

docs/install/troubleshooting-installation-issues.md

@@ -23,9 +23,9 @@ ms.technology: vs-installation
 
 This troubleshooting guide includes step-by-step instructions that should resolve most installation issues.
 
-## Troubleshoot an online installation
+## Online installations
 
-The following steps are optimized for a typical online installation. For an issue that affects an offline installation, please see [How to troubleshoot an offline installation](#troubleshoot-an-offline-installation).
+The following steps are optimized for a typical online installation. For an issue that affects an offline installation, please see [How to troubleshoot an offline installation](#offline-installations).
 
 ### Step 1 - Check whether this problem is a known issue
 
@@ -76,7 +76,7 @@ In some situations, such as those related to corrupted files, the problems might
 
 ::: moniker range="vs-2017"
 
-1. Collect your setup logs. See [How to get the Visual Studio installation logs](#get-installation-logs) for details.
+1. Collect your setup logs. See [How to get the Visual Studio installation logs](#installation-logs) for details.
 2. Open the Visual Studio Installer, and then click **Report a problem** to open the Visual Studio Feedback tool.
 ![You can tab to the Provide Feedback button to open the feedback tool](media/report-a-problem.png)
 3. Give your problem report a title, and provide relevant details. Click **Next** to go to the **Attachments** section, and then attach the generated log file (typically, the file is at `%TEMP%\vslogs.zip`).
@@ -86,7 +86,7 @@ In some situations, such as those related to corrupted files, the problems might
 
 ::: moniker range="vs-2019"
 
-1. Collect your setup logs. See [How to get the Visual Studio installation logs](#get-installation-logs) for details.
+1. Collect your setup logs. See [How to get the Visual Studio installation logs](#installation-logs) for details.
 2. Open the Visual Studio Installer, and then click **Report a problem** to open the Visual Studio Feedback tool.
 ![You can tab to the Provide Feedback button to open the feedback tool](media/vs-2019/vs-installer-report-problem.png)
 3. Give your problem report a title, and provide relevant details. Click **Next** to go to the **Attachments** section, and then attach the generated log file (typically, the file is at `%TEMP%\vslogs.zip`).
@@ -106,7 +106,7 @@ As a last resort, you can [remove Visual Studio](remove-visual-studio.md) to rem
 
 If none of the previous steps help you successfully install or upgrade Visual Studio, contact us by using our [**live chat**](https://visualstudio.microsoft.com/vs/support/#talktous) support option (English only) for further assistance.
 
-## Troubleshoot an offline installation
+## Offline installations
 
 Here is a table of known issues and some workarounds that might help you when you install from a local layout.
 
@@ -115,7 +115,7 @@ Here is a table of known issues and some workarounds that might help you when yo
 | Users do not have access to files. | permissions (ACLs) | Make sure that you adjust the permissions (ACLs) so that they grant Read access to other users  *before* you share the offline install. |
 | New workloads, components, or languages fail to install.  | `--layout`  | Make sure that you have internet access if you install from a partial layout and select workloads, components, or languages that were not downloaded previously in that partial layout. |
 
-## Get installation logs
+## Installation logs
 
 Setup logs are needed to troubleshoot most installation issues. When you submit an issue by using [Report a Problem](../ide/how-to-report-a-problem-with-visual-studio.md) in the Visual Studio Installer, these logs are automatically included in your report.
 
@@ -131,7 +131,7 @@ To collect the logs:
 > [!NOTE]
 > The tool must be run under the same user account that the failed installation was run under. If you are running the tool from a different user account, set the `–user:<name>` option to specify the user account under which the failed installation was run. Run `Collect.exe -?` from an administrator command prompt for additional options and usage information.
 
-## Get live help
+## Live help
 
 If the solutions listed in this troubleshooting guide do not help you to successfully install or upgrade Visual Studio, use our [**live chat**](https://visualstudio.microsoft.com/vs/support/#talktous) support option (English only) for further assistance.
 

docs/install/use-command-line-parameters-to-install-visual-studio.md

@@ -2,7 +2,7 @@
 title: "Use command-line parameters to install Visual Studio"
 titleSuffix: ""
 description: "Learn how to use command-line parameters to control or customize your Visual Studio installation."
-ms.date: 04/26/2019
+ms.date: 09/11/2019
 ms.custom: "seodec18"
 ms.topic: conceptual
 f1_keywords:
@@ -50,7 +50,7 @@ The command-line options are used in conjunction with the setup bootstrapper, wh
 
 > Syntax: `vs_enterprise.exe [command] <options>...`
 
-(Replace `vs_enterprise.exe` as appropriate for the product edition you're installing.)
+Replace `vs_enterprise.exe` as appropriate for the product edition you're installing. (Alternatively, you can use `vs_installer.exe`.)
 
 >[!TIP]
 > For more examples of how to use the command line to install Visual Studio, see the [Command-line parameter examples](command-line-parameter-examples.md) page.

docs/msbuild/how-to-extend-the-visual-studio-build-process.md

@@ -18,16 +18,19 @@ ms.workload:
 # How to: Extend the Visual Studio build process
 The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process is defined by a series of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] *.targets* files that are imported into your project file. One of these imported files, *Microsoft.Common.targets*, can be extended to allow you to run custom tasks at several points in the build process. This article explains two methods you can use to extend the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] build process:
 
-- Overriding specific predefined targets defined in *Microsoft.Common.targets*.
+- Overriding specific predefined targets defined in the common targets (*Microsoft.Common.targets* or the files that it imports).
 
-- Overriding the "DependsOn" properties defined in *Microsoft.Common.targets*.
+- Overriding the "DependsOn" properties defined in the common targets.
 
 ## Override predefined targets
-The *Microsoft.Common.targets* file contains a set of predefined empty targets that is called before and after some of the major targets in the build process. For example, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] calls the `BeforeBuild` target before the main `CoreBuild` target and the `AfterBuild` target after the `CoreBuild` target. By default, the empty targets in *Microsoft.Common.targets* do nothing, but you can override their default behavior by defining the targets you want in a project file that imports *Microsoft.Common.targets*. By overriding the predefined targets, you can use [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks to give you more control over the build process.
+The common targets contains a set of predefined empty targets that is called before and after some of the major targets in the build process. For example, [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] calls the `BeforeBuild` target before the main `CoreBuild` target and the `AfterBuild` target after the `CoreBuild` target. By default, the empty targets in the common targets do nothing, but you can override their default behavior by defining the targets you want in a project file that imports the common targets. By overriding the predefined targets, you can use [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] tasks to give you more control over the build process.
+
+> [!NOTE]
+> SDK-style projects have an implicit import of targets *after the last line of the project file*. This means that you cannot override default targets unless you specify your imports manually as described in [How to: Use MSBuild project SDKs](how-to-use-project-sdk.md).
 
 #### To override a predefined target
 
-1. Identify a predefined target in *Microsoft.Common.targets* that you want to override. See the table below for the complete list of targets that you can safely override.
+1. Identify a predefined target in the common targets that you want to override. See the table below for the complete list of targets that you can safely override.
 
 2. Define the target or targets at the end of your project file, immediately before the `</Project>` tag. For example:
 
@@ -45,7 +48,7 @@ The *Microsoft.Common.targets* file contains a set of predefined empty targets t
 
 3. Build the project file.
 
-The following table shows all of the targets in *Microsoft.Common.targets* that you can safely override.
+The following table shows all of the targets in the common targets that you can safely override.
 
 |Target name|Description|
 |-----------------|-----------------|
@@ -60,7 +63,7 @@ The following table shows all of the targets in *Microsoft.Common.targets* that
 ## Override DependsOn properties
 Overriding predefined targets is an easy way to extend the build process, but, because [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] evaluates the definition of targets sequentially, there is no way to prevent another project that imports your project from overriding the targets you already have overridden. So, for example, the last `AfterBuild` target defined in the project file, after all other projects have been imported, will be the one that is used during the build.
 
-You can guard against unintended overrides of targets by overriding the DependsOn properties that are used in `DependsOnTargets` attributes throughout the *Microsoft.Common.targets* file. For example, the `Build` target contains a `DependsOnTargets` attribute value of `"$(BuildDependsOn)"`. Consider:
+You can guard against unintended overrides of targets by overriding the DependsOn properties that are used in `DependsOnTargets` attributes throughout the common targets. For example, the `Build` target contains a `DependsOnTargets` attribute value of `"$(BuildDependsOn)"`. Consider:
 
 ```xml
 <Target Name="Build" DependsOnTargets="$(BuildDependsOn)"/>
@@ -101,7 +104,7 @@ Projects that import your project files can override these properties without ov
 
 #### To override a DependsOn property
 
-1. Identify a predefined DependsOn property in *Microsoft.Common.targets* that you want to override. See the table below for a list of the commonly overridden DependsOn properties.
+1. Identify a predefined DependsOn property in the common targets that you want to override. See the table below for a list of the commonly overridden DependsOn properties.
 
 2. Define another instance of the property or properties at the end of your project file. Include the original property, for example `$(BuildDependsOn)`, in the new property.
 

docs/msbuild/msbuild-target-framework-and-target-platform.md

@@ -52,7 +52,10 @@ The target framework is specified in the `TargetFrameworkVersion` property in th
 
  A *target profile* is a subset of a target framework. For example, the .NET Framework 4 Client profile does not include references to the MSBuild assemblies.
 
- The target profile is specified in the `TargetFrameworkProfile` property in a project file. You can change the target profile by using the target-framework control in the project property pages in the IDE. For more information, see [How to: Target a version of the .NET Framework](../ide/how-to-target-a-version-of-the-dotnet-framework.md).
+ > [!NOTE]
+ > Target profiles apply only to [portable class libraries](/dotnet/standard/cross-platform/cross-platform-development-with-the-portable-class-library).
+
+ The target profile is specified in the `TargetFrameworkProfile` property in a project file. You can change the target profile by using the target-framework control in the project property pages in the IDE.
 
 ```xml
 <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>

docs/msbuild/visual-studio-integration-msbuild.md

@@ -170,7 +170,7 @@ Condition=" '$(Something)|$(Configuration)|$(SomethingElse)' == 'xxx|Debug|yyy'
    The project system calls a target with the well-known name `ResolveNativeReferences`. This target should produce items with the item type name `NativeReferenceFile`. The items should have all the metadata from the input items passed through, in addition to a new piece of metadata named `OriginalItemSpec`, containing the original item specification of the reference.
 
 ## Performance shortcuts
- If you start debugging in the Visual Studio UI (either by choosing the F5 key or by choosing **Debug** > **Start Debugging** on the menu bar), the build process uses a fast update check to improve performance. In some cases where customized builds create files that get built in turn, the fast update check does not correctly identify the changed files. Projects that need more thorough update checks can turn off the fast checking by setting the environment variable `DISABLEFASTUPTODATECHECK=1`. Alternatively, projects can set this as an MSBuild property in the project or in a file the project imports.
+ If you use the Visual Studio IDE to start debugging (either by choosing the F5 key or by choosing **Debug** > **Start Debugging** on the menu bar) or to build your project (for example, **Build** > **Build Solution**), the build process uses a fast update check to improve performance. In some cases where customized builds create files that get built in turn, the fast update check does not correctly identify the changed files. Projects that need more thorough update checks can turn off the fast checking by setting the environment variable `DISABLEFASTUPTODATECHECK=1`. Alternatively, projects can set this as an MSBuild property in the project or in a file the project imports.
 
  For regular builds in Visual Studio, the fast update check doesn't apply, and the project will build as if you invoked the build at a command prompt.
 

docs/msbuild/what-s-new-in-msbuild-15-0.md

@@ -8,7 +8,7 @@ ms.author: mikejo
 manager: jillfra
 ms.workload:
   - "multiple"
-monikerRange: "vs-2017"
+monikerRange: ">=vs-2017"
 ---
 # What's new in MSBuild 15