Merge branch 'master' of github.com:MicrosoftDocs/visualstudio-docs-pr into msbuild

Author: ghogen

docs/deployment/how-to-specify-an-alternate-location-for-deployment-updates.md

@@ -40,9 +40,9 @@ You can install your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_m
 
 1. Open a .NET Framework command prompt.
 
-2. Set the update location using the following command. In this example, *HelloWorld.exe.application* is the path to your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application manifest, which always has the .application extension, and *<http://adatum.com/Update/Path>* is the URL that [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] will check for application updates.
+2. Set the update location using the following command. In this example, *HelloWorld.exe.application* is the path to your [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application manifest, which always has the .application extension, and `http://adatum.com/Update/Path` is the URL that [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] will check for application updates.
 
-    **Mage -Update HelloWorld.exe.application -ProviderUrl http://adatum.com/Update/Path**
+    **Mage -Update HelloWorld.exe.application -ProviderUrl http:\//adatum.com/Update/Path**
 
 3. Save the file.
 

docs/deployment/toc.yml

@@ -41,11 +41,11 @@
   - name: C++
     items:
     - name: Deploy a C/C++ app
-      href: /cpp/ide/walkthrough-deploying-a-visual-cpp-application-by-using-a-setup-project
+      href: /cpp/windows/walkthrough-deploying-a-visual-cpp-application-by-using-a-setup-project
     - name: Package a desktop app for Microsoft Store
       href: /windows/msix/desktop/desktop-to-uwp-packaging-dot-net
     - name: Deploy a C++/CLR app using ClickOnce...
-      href: /cpp/ide/clickonce-deployment-for-visual-cpp-applications
+      href: /cpp/windows/clickonce-deployment-for-visual-cpp-applications
   - name: UWP
     items:
     - name: Package a UWP app by using Visual Studio

docs/get-started/csharp/breadcrumb/toc.yml

@@ -8,4 +8,4 @@
     items:
     - name: C#
       tocHref: /visualstudio/csharp/
-      topicHref: /visualstudio/csharp/index
+      topicHref: /visualstudio/get-started/csharp/index

docs/get-started/visual-basic/breadcrumb/toc.yml

@@ -8,4 +8,4 @@
     items:
     - name: Visual Basic
       tocHref: /visualstudio/visual-basic
-      topicHref: /visualstudio/visual-basic/index
+      topicHref: /visualstudio/get-started/visual-basic/index

docs/install/using-visual-studio-vm.md

@@ -2,7 +2,7 @@
 title: Using Visual Studio on an Azure Virtual Machine
 titleSuffix: ''
 description: Learn how to use Visual Studio on an Azure Virtual Machine
-ms.date: 12/06/2019
+ms.date: 04/23/2020
 ms.custom: seodec18
 ms.topic: conceptual
 helpviewer_keywords:
@@ -30,10 +30,10 @@ Images for the most recent major versions, Visual Studio 2019, Visual Studio 201
 
 | Release version                                                                                                                                          | Editions              |    Product version    |
 |:--------------------------------------------------------------------------------------------------------------------------------------------------------:|:---------------------:|:-----------------------:|
-| [Visual Studio 2019: Latest (Version 16.4)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019latest?tab=Overview) | Enterprise, Community | Version 16.4.0    |
-| [Visual Studio 2019: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019?tab=Overview)                         | Enterprise            | Version 16.0.9    |
-| [Visual Studio 2017: Latest (Version 15.9)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)           | Enterprise, Community | Version 15.9.17   |
-| [Visual Studio 2017: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)                             | Enterprise, Community | Version 15.0.27   |
+| [Visual Studio 2019: Latest (Version 16.5)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019latest?tab=Overview) | Enterprise, Community | Version 16.5.4    |
+| [Visual Studio 2019: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio2019?tab=Overview)                         | Enterprise            | Version 16.0.13    |
+| [Visual Studio 2017: Latest (Version 15.9)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)           | Enterprise, Community | Version 15.9.22   |
+| [Visual Studio 2017: RTW](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)                             | Enterprise, Community | Version 15.0.28   |
 | [Visual Studio 2015: Latest (Update 3)](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftvisualstudio.visualstudio?tab=Overview)               | Enterprise, Community | Version 14.0.25431.01 |
 
 > [!NOTE]

docs/install/visual-studio-build-numbers-and-release-dates.md

@@ -5,7 +5,7 @@ description: A list of released versions and build numbers for Visual Studio, so
 author: ornellaalt
 ms.author: ornella
 manager: jillfra
-ms.date: 04/16/2020
+ms.date: 04/23/2020
 ms.topic: reference
 ms.workload:
 - multiple
@@ -23,6 +23,7 @@ The following table lists the build numbers and release dates for Visual Studio
 
 | **Version**| **Channel** | **Release date** | **Build version** |
 | ---------------------- | ----------- | ---------------- | ----------------- |
+| 16.6.0 | Preview 4 | April 23, 2020 | 16.6.30021.99 |
 | 16.6.0 | Preview 3 | April 16, 2020 | 16.6.30014.187 |
 | 16.0.13 | Release | April 14, 2020 | 16.0.28803.718 |
 | 16.4.7 | Release | April 14, 2020 | 16.4.30011.19 |

docs/msbuild/how-to-specify-which-target-to-build-first.md

@@ -15,7 +15,7 @@ ms.workload:
 ---
 # How to: Specify which target to build first
 
-A project file can contain one or more `Target` elements that define how the project is built. The Microsoft Build Engine (MSBuild) engine builds the first project it finds, and any dependencies, unless the project file contains a `DefaultTargets` attribute, an `InitialTargets` attribute, or a target is specified at the command line using the **-target** switch.
+A project file can contain one or more `Target` elements that define how the project is built. The Microsoft Build Engine (MSBuild) engine builds the first target it finds, and any dependencies, unless the project file contains a `DefaultTargets` attribute, an `InitialTargets` attribute, or a target is specified at the command line using the **-target** switch.
 ## Use the InitialTargets attribute
 
 The `InitialTargets` attribute of the `Project` element specifies a target that will run first, even if targets are specified on the command line or in the `DefaultTargets` attribute.

docs/msbuild/msbuild-command-line-reference.md

@@ -74,7 +74,7 @@ MSBuild.exe [Switches] [ProjectFile]
 |-distributedFileLogger|-dfl|Log the build output of each MSBuild node to its own file. The initial location for these files is the current directory. By default, the files are named *MSBuild\<NodeId>.log*. You can use the **-fileLoggerParameters** switch to specify the location of the files and other parameters for the fileLogger.<br /><br /> If you name a log file by using the **-fileLoggerParameters** switch, the distributed logger will use that name as a template and append the node ID to that name when creating a log file for each node.|
 |-distributedLogger:<br /><br /> `central logger`*<br /><br /> `forwarding logger`|-dl:`central logger`*`forwarding logger`|Log events from MSBuild, attaching a different logger instance to each node. To specify multiple loggers, specify each logger separately.<br /><br /> You use the logger syntax to specify a logger. For the logger syntax, see the **-logger** switch below.<br /><br /> The following examples show how to use this switch:<br /><br /> `-dl:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral`<br /><br /> `-dl:MyLogger,C:\My.dll*ForwardingLogger,C:\Logger.dll`|
 |-fileLogger<br /><br /> *[number]*|-fl[`number`]|Log the build output to a single file in the current directory. If you don't specify `number`, the output file is named *msbuild.log*. If you specify `number`, the output file is named *msbuild\<n>.log*, where \<n> is `number`. `Number` can be a digit from 1 to 9.<br /><br /> You can use the **-fileLoggerParameters** switch to specify the location of the file and other parameters for the fileLogger.|
-|-fileLoggerParameters:[number]<br /><br /> `parameters`|-flp:[ `number`] `parameters`|Specifies any extra parameters for the file logger and the distributed file logger. The presence of this switch implies that the corresponding -**filelogger[**`number`**]** switch is present. `Number` can be a digit from 1 to 9.<br /><br /> You can use all parameters that are listed for **-consoleloggerparameters**. You can also use one or more of the following parameters:<br /><br /> -   **LogFile**. The path to the log file into which the build log is written. The distributed file logger prefixes this path to the names of its log files.<br />-   **Append**. Determines whether the build log is appended to the log file or overwrites it. When you set the switch, the build log is appended to the log file. When the switch is not present, the contents of an existing log file are overwritten.<br />     If you include the append switch, no matter whether it is set to true or false, the log is appended. If you do not include the append switch, the log is overwritten.<br />     In this case the file is overwritten: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log`<br />     In this case the file is appended: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log;append=true`<br />     In this case the file is appended: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log;append=false`<br />-   **Encoding**. Specifies the encoding for the file (for example, UTF-8, Unicode, or ASCII).<br /><br /> The following example generates separate log files for warnings and errors:<br /><br /> `-flp1:logfile=errors.txt;errorsonly -flp2:logfile=warnings.txt;warningsonly`<br /><br /> The following examples show other possibilities:<br /><br /> `-fileLoggerParameters:LogFile=MyLog.log;Append; Verbosity=diagnostic;Encoding=UTF-8`<br /><br /> `-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum`<br /><br /> `-flp1:warningsonly;logfile=msbuild.wrn`<br /><br /> `-flp2:errorsonly;logfile=msbuild.err`|
+|-fileLoggerParameters:[number]<br /><br /> `parameters`|-flp[ `number`]: `parameters`|Specifies any extra parameters for the file logger and the distributed file logger. The presence of this switch implies that the corresponding -**filelogger[**`number`**]** switch is present. `Number` can be a digit from 1 to 9.<br /><br /> You can use all parameters that are listed for **-consoleloggerparameters**. You can also use one or more of the following parameters:<br /><br /> -   **LogFile**. The path to the log file into which the build log is written. The distributed file logger prefixes this path to the names of its log files.<br />-   **Append**. Determines whether the build log is appended to the log file or overwrites it. When you set the switch, the build log is appended to the log file. When the switch is not present, the contents of an existing log file are overwritten.<br />     If you include the append switch, no matter whether it is set to true or false, the log is appended. If you do not include the append switch, the log is overwritten.<br />     In this case the file is overwritten: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log`<br />     In this case the file is appended: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log;append=true`<br />     In this case the file is appended: `msbuild myfile.proj -l:FileLogger,Microsoft.Build;logfile=MyLog.log;append=false`<br />-   **Encoding**. Specifies the encoding for the file (for example, UTF-8, Unicode, or ASCII).<br /><br /> The following example generates separate log files for warnings and errors:<br /><br /> `-flp1:logfile=errors.txt;errorsonly -flp2:logfile=warnings.txt;warningsonly`<br /><br /> The following examples show other possibilities:<br /><br /> `-fileLoggerParameters:LogFile=MyLog.log;Append; Verbosity=diagnostic;Encoding=UTF-8`<br /><br /> `-flp:Summary;Verbosity=minimal;LogFile=msbuild.sum`<br /><br /> `-flp1:warningsonly;logfile=msbuild.wrn`<br /><br /> `-flp2:errorsonly;logfile=msbuild.err`|
 |-logger:<br /><br /> `logger`|-l:`logger`|Specifies the logger to use to log events from MSBuild. To specify multiple loggers, specify each logger separately.<br /><br /> Use the following syntax for `logger`: `[``LoggerClass``,]``LoggerAssembly``[;``LoggerParameters``]`<br /><br /> Use the following syntax for `LoggerClass`: `[``PartialOrFullNamespace``.]``LoggerClassName`<br /><br /> You don't have to specify the logger class if the assembly contains exactly one logger.<br /><br /> Use the following syntax for `LoggerAssembly`: `{``AssemblyName``[,``StrongName``] &#124;` `AssemblyFile``}`<br /><br /> Logger parameters are optional and are passed to the logger exactly as you enter them.<br /><br /> The following examples use the **-logger** switch.<br /><br /> `-logger:XMLLogger,MyLogger,Version=1.0.2,Culture=neutral`<br /><br /> `-logger:XMLLogger,C:\Loggers\MyLogger.dll;OutputAsHTML`|
 |-noConsoleLogger|-noconlog|Disable the default console logger, and don't log events to the console.|
 

docs/msbuild/msbuild-conditions.md

@@ -43,7 +43,7 @@ You can use string methods in conditions, as shown in the following example, in
         <TargetFrameworks>net45;net48;netstandard2.1;netcoreapp2.1;netcoreapp3.1</TargetFrameworks>
     </PropertyGroup>
 
-    <PropertyGroup Condition="'$(TargetFramework.TrimEnd('0123456789.'))' == 'net'">
+    <PropertyGroup Condition="'$(TargetFramework.TrimEnd(`0123456789.`))' == 'net'">
         <!-- Properties for .NET Framework -->
     </PropertyGroup>
 

docs/msbuild/msbuild-task.md

@@ -36,6 +36,7 @@ Builds MSBuild projects from another MSBuild project.
 | `RemoveProperties` | Optional `String` parameter.<br /><br /> Specifies the set of global properties to remove. |
 | `RunEachTargetSeparately` | Optional `Boolean` parameter.<br /><br /> If `true`, the MSBuild task invokes each target in the list passed to MSBuild one at a time, instead of at the same time. Setting this parameter to `true` guarantees that subsequent targets are invoked even if previously invoked targets failed. Otherwise, a build error would stop invocation of all subsequent targets. Default is `false`. |
 | `SkipNonexistentProjects` | Optional `Boolean` parameter.<br /><br /> If `true`, project files that do not exist on the disk will be skipped. Otherwise, such projects will cause an error. |
+|`SkipNonexistentTargets`|Optional `Boolean` parameter.<br /><br /> If `true`, project files that exist but do not contain the named `Targets` will be skipped. Otherwise, such projects will cause an error. Introduced in MSBuild 15.5.|
 | `StopOnFirstFailure` | Optional `Boolean` parameter.<br /><br /> If `true`, when one of the projects fails to build, no more projects will be built. Currently this is not supported when building in parallel (with multiple processors). |
 | `TargetAndPropertyListSeparators` | Optional `String[]` parameter.<br /><br /> Specifies a list of targets and properties as `Project` item metadata). Separators will be un-escaped before processing. e.g. %3B (an escaped ';') will be treated as if it were an un-escaped ';'. |
 | `TargetOutputs` | Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` read-only output parameter.<br /><br /> Returns the outputs of the built targets from all the project files. Only the outputs from the targets that were specified are returned, not any outputs that may exist on targets that those targets depend on.<br /><br /> The `TargetOutputs` parameter also contains the following metadata:<br /><br /> -   `MSBuildSourceProjectFile`: The MSBuild project file that contains the target that set the outputs.<br />-   `MSBuildSourceTargetName`: The target that set the outputs. **Note:**  If you want to identify the outputs from each project file or target separately, run the `MSBuild` task separately for each project file or target. If you run the `MSBuild` task only once to build all the project files, the outputs of all the targets are collected into one array. |