Merge pull request #10401 from ghogen/msbuild-content-updates-sep22

MSBuild: update articles for Visual Studio 2022

Author: BCS2022

docs/ide/how-to-view-save-and-configure-build-log-files.md

@@ -2,7 +2,7 @@
 title: 'How to: View, save, and configure build log files | Microsoft Docs'
 description: Learn how you can view, save, and configure build log files. These files provide useful information for tasks like troubleshooting a build failure.
 ms.custom: SEO-VS-2020
-ms.date: 08/28/2019
+ms.date: 09/12/2022
 ms.technology: vs-ide-compile
 ms.topic: how-to
 ms.assetid: 75d38b76-26d6-4f43-bbe7-cbacd7cc81e7
@@ -18,7 +18,7 @@ ms.workload:
 
 After you build a project in the Visual Studio IDE, you can view information about that build in the **Output** window. By using this information, you can, for example, troubleshoot a build failure.
 
-- For C++ projects, you can also view the same information in a log file that's created and saved when you build a project. 
+- For C++ projects, you can also view the same information in a log file that's created and saved when you build a project.
 
 - For managed code projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a log file.
 
@@ -28,7 +28,7 @@ If you build any kind of project by using MSBuild, you can create a log file to
 
 ## To view the build log file for a C++ project
 
-1. In **Windows Explorer** or **File Explorer**, open the following file (relative to the project root folder): *Release*\\{ProjectName}.Log* or *Debug\\{ProjectName}.log*
+1. In **Windows Explorer** or **File Explorer**, open the following file (relative to the project root folder): *Release\\{ProjectName}.Log* or *Debug\\{ProjectName}.log*
 
 ## To create a build log file for a managed-code project
 

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

@@ -2,7 +2,7 @@
 title: MSBuild Target Framework and Target Platform | Microsoft Docs
 description: Learn how to build an MSBuild project to run on a target .NET Framework version, and a target platform or software architecture.
 ms.custom: SEO-VS-2020
-ms.date: 11/04/2016
+ms.date: 09/12/2022
 ms.topic: conceptual
 ms.assetid: df6517c5-edd6-4cc4-97ad-b3cdfc78e799
 author: ghogen

docs/msbuild/target-build-order.md

@@ -2,7 +2,7 @@
 title: Target Build Order | Microsoft Docs
 description: Learn how to specify the order in which MSBuild targets are run, if the input to one target depends on the output of another target.
 ms.custom: SEO-VS-2020
-ms.date: 05/02/2019
+ms.date: 09/12/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - msbuild, build order
@@ -25,7 +25,7 @@ Targets must be ordered if the input to one target depends on the output of anot
 
 - `DependsOnTargets`. This `Target` attribute specifies targets that must run before this target can run.
 
-- `BeforeTargets` and `AfterTargets`. These `Target` attributes specify that this target should run before or after the specified targets (MSBuild 4.0).
+- `BeforeTargets` and `AfterTargets`. These `Target` attributes specify that this target should run before or after the specified targets.
 
 A target is never run twice during a build, even if a subsequent target in the build depends on it. Once a target has been run, its contribution to the build is complete.
 
@@ -81,7 +81,7 @@ tells MSBuild that the `Serve` target depends on the `Chop` target and the `Cook
 
 ## BeforeTargets and AfterTargets
 
-In MSBuild 4.0 and later, you can specify target order by using the `BeforeTargets` and `AfterTargets` attributes.
+You can specify target order by using the `BeforeTargets` and `AfterTargets` attributes.
 
 Consider the following script.
 

docs/msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md

@@ -1,8 +1,7 @@
 ---
 title: Create an MSBuild project file from scratch
 description: Walk through creating an MSBuild project file from scratch to understand how the XML is organized and how you can change it to control a build.
-ms.custom: SEO-VS-2020
-ms.date: 11/04/2016
+ms.date: 09/12/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - MSBuild, tutorial
@@ -19,7 +18,7 @@ ms.workload:
 Programming languages that target the .NET Framework use MSBuild project files to describe and control the application build process. When you use Visual Studio to create an MSBuild project file, the appropriate XML is added to the file automatically. However, you may find it helpful to understand how the XML is organized and how you can change it to control a build.
 
 > [!NOTE]
-> This tutorial works only with .NET Framework 4.x and earlier, not .NET Core or .NET 5 and later.
+> This article is appropriate if you want to learn the basic fundamentals of how MSBuild works independently of any SDK. Building with an SDK, such as when you use `dotnet build` or you add the `Sdk` attribute to the root project element, is not covered in this article. See [.NET Project SDKs](/dotnet/core/project-sdk/overview).
 
  For information about creating a project file for a C++ project, see [MSBuild (C++)](/cpp/build/msbuild-visual-cpp).
 
@@ -45,7 +44,7 @@ Programming languages that target the .NET Framework use MSBuild project files t
 
 This walkthrough shows how to build the project at the command prompt and examine the results. For more information about MSBuild and how to run MSBuild at the command prompt, see [Walkthrough: Use MSBuild](../msbuild/walkthrough-using-msbuild.md).
 
-To complete the walkthrough, you must have Visual Studio installed because it includes MSBuild and the Visual C# compiler, which are required for the walkthrough.
+To complete the walkthrough, you must have Visual Studio installed because it includes MSBuild and the C# compiler, which are required for the walkthrough.
 
 ## Extend the path
 
@@ -57,11 +56,9 @@ Before you can use MSBuild, you must extend the PATH environment variable to inc
 
 1. At the command prompt, browse to the folder where you want to create the application, for example, *\My Documents\\* or *\Desktop\\*.
 
-2. Type **md HelloWorld** to create a subfolder named *\HelloWorld\\*.
+1. Create a subfolder named *\HelloWorld\\* and change directory to go inside it.
 
-3. Type **cd HelloWorld** to change to the new folder.
-
-4. Start Notepad or another text editor, and then type the following code.
+1. In a text editor, create a new file *HelloWorld.cs* and then copy and paste the following code:
 
     ```csharp
     using System;
@@ -79,15 +76,13 @@ Before you can use MSBuild, you must extend the PATH environment variable to inc
     }
     ```
 
-5. Save this source code file and name it *Helloworld.cs*.
-
-6. Build the application by typing **csc helloworld.cs** at the command prompt.
+1. Build the application by typing **csc helloworld.cs** at the command prompt.
 
-7. Test the application by typing **helloworld** at the command prompt.
+1. Test the application by typing **helloworld** at the command prompt.
 
      The **Hello, world!** message should be displayed.
 
-8. Delete the application by typing **del helloworld.exe** at the command prompt.
+1. Delete the executable.
 
 ## Create a minimal MSBuild project file
 
@@ -101,56 +96,51 @@ Before you can use MSBuild, you must extend the PATH environment variable to inc
 
 - A `Target` node to contain tasks that are required to build the application.
 
-- A `Task` element to start the Visual C# compiler to build the application.
+- A `Task` element to start the C# compiler to build the application.
 
 ### To create a minimal MSBuild project file
 
-1. In the text editor, create a new file and enter these two lines:
+1. In the text editor, create a new file *HelloWorld.csproj* and enter the following code:
 
     ```xml
-    <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+    <Project>
+      <ItemGroup>
+        <Compile Include="helloworld.cs" />
+      </ItemGroup>
     </Project>
     ```
 
-2. Insert this `ItemGroup` node as a child element of the `Project` node:
-
-    ```xml
-    <ItemGroup>
-      <Compile Include="helloworld.cs" />
-    </ItemGroup>
-    ```
-
-     Notice that this `ItemGroup` already contains an item element.
+    This `ItemGroup` contains an item element `Compile` and specifies one source file as an item.
 
-3. Add a `Target` node as a child element of the `Project` node. Name the node `Build`.
+1. Add a `Target` node as a child element of the `Project` node. Name the node `Build`.
 
     ```xml
     <Target Name="Build">
     </Target>
     ```
 
-4. Insert this task element as a child element of the `Target` node:
+1. Insert this task element as a child element of the `Target` node:
 
     ```xml
     <Csc Sources="@(Compile)"/>
     ```
 
-5. Save this project file and name it *Helloworld.csproj*.
+1. Save this project file and name it *Helloworld.csproj*.
 
 Your minimal project file should resemble the following code:
 
 ```xml
-<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+<Project>
   <ItemGroup>
-    <Compile Include="helloworld.cs" />
+    <Compile Include="helloworld.cs"/>
   </ItemGroup>
   <Target Name="Build">
-    <Csc Sources="@(Compile)"/>  
+    <Csc Sources="@(Compile)"/>
   </Target>
 </Project>
 ```
 
-Tasks in the Build target are executed sequentially. In this case, the Visual C# compiler `Csc` task is the only task. It expects a list of source files to compile, and this is given by the value of the `Compile` item. The `Compile` item references just one source file, *Helloworld.cs*.
+Tasks in the Build target are executed sequentially. In this case, the C# compiler `Csc` task is the only task. It expects a list of source files to compile, and this is given by the value of the `Compile` item. The `Compile` item references just one source file, *Helloworld.cs*.
 
 > [!NOTE]
 > In the item element, you can use the asterisk wildcard character (\*) to reference all files that have the *.cs* file name extension, as follows:
@@ -165,7 +155,7 @@ Tasks in the Build target are executed sequentially. In this case, the Visual C#
 
 1. At the command prompt, type **msbuild helloworld.csproj -t:Build**.
 
-     This builds the Build target of the Helloworld project file by invoking the Visual C# compiler to create the Helloworld application.
+     This builds the Build target of the Helloworld project file by invoking the C# compiler to create the Helloworld application.
 
 2. Test the application by typing **helloworld**.
 
@@ -186,9 +176,9 @@ Tasks in the Build target are executed sequentially. In this case, the Visual C#
 
 ### To add build properties
 
-1. Delete the existing application by typing **del helloworld.exe** at the command prompt.
+1. Delete the existing application executable (later, you'll add a `Clean` target to handle the deletion of old output files).
 
-2. In the project file, insert this `PropertyGroup` element just after the opening `Project` element:
+1. In the project file, insert this `PropertyGroup` element just after the opening `Project` element:
 
     ```xml
     <PropertyGroup>
@@ -197,28 +187,28 @@ Tasks in the Build target are executed sequentially. In this case, the Visual C#
     </PropertyGroup>
     ```
 
-3. Add this task to the Build target, just before the `Csc` task:
+1. Add this task to the Build target, just before the `Csc` task:
 
     ```xml
-    <MakeDir Directories="$(OutputPath)"      Condition="!Exists('$(OutputPath)')" />
+    <MakeDir Directories="$(OutputPath)" Condition="!Exists('$(OutputPath)')" />
     ```
 
-     The `MakeDir` task creates a folder that is named by the `OutputPath` property, provided that no folder by that name currently exists.
+    The `MakeDir` task creates a folder that is named by the `OutputPath` property, provided that no folder by that name currently exists.
 
-4. Add this `OutputAssembly` attribute to the `Csc` task:
+1. Add this `OutputAssembly` attribute to the `Csc` task:
 
     ```xml
     <Csc Sources="@(Compile)" OutputAssembly="$(OutputPath)$(AssemblyName).exe" />
     ```
 
-     This instructs the Visual C# compiler to produce an assembly that is named by the `AssemblyName` property and to put it in the folder that is named by the `OutputPath` property.
+     This instructs the C# compiler to produce an assembly that is named by the `AssemblyName` property and to put it in the folder that is named by the `OutputPath` property.
 
-5. Save your changes.
+1. Save your changes.
 
 Your project file should now resemble the following code:
 
 ```xml
-<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+<Project>
   <PropertyGroup>
     <AssemblyName>MSBuildSample</AssemblyName>
     <OutputPath>Bin\</OutputPath>
@@ -252,13 +242,13 @@ Your project file should now resemble the following code:
 
 1. At the command prompt, type **msbuild helloworld.csproj -t:Build**.
 
-     This creates the *\Bin\\* folder and then invokes the Visual C# compiler to create the *MSBuildSample* application and puts it in the *\Bin\\* folder.
+     This creates the *\Bin\\* folder and then invokes the C# compiler to create the *MSBuildSample* application and puts it in the *\Bin\\* folder.
 
 2. To verify that the *\Bin\\* folder has been created, and that it contains the *MSBuildSample* application, type **dir Bin**.
 
-3. Test the application by typing **Bin\MSBuildSample**.
+3. Test the application by typing **Bin\MSBuildSample** to run the executable.
 
-     The **Hello, world!** message should be displayed.
+    The **Hello, world!** message should be displayed.
 
 ## Add build targets
 
@@ -286,15 +276,15 @@ Now that you have multiple targets, you can set the Build target as the default
 2. Add this `DefaultTargets` attribute to the opening `Project` element:
 
     ```xml
-    <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+    <Project DefaultTargets="Build">
     ```
 
      This sets the Build target as the default target.
 
 Your project file should now resemble the following code:
 
 ```xml
-<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+<Project DefaultTargets="Build">
   <PropertyGroup>
     <AssemblyName>MSBuildSample</AssemblyName>
     <OutputPath>Bin\</OutputPath>
@@ -333,7 +323,7 @@ Your project file should now resemble the following code:
 
 2. To verify that the *\Bin\\* folder contains both the *MSBuildSample* application and the new *Greetings* application, type **dir Bin**.
 
-3. Test the Greetings application by typing **Bin\Greetings**.
+3. Test the Greetings application (for example, by typing **Bin\Greetings** on Windows).
 
      The **Hello, world!** message should be displayed.
 
@@ -380,16 +370,12 @@ Your project file should now resemble the following code:
 
      Remember that *helloworld.csproj* is the default project file, and that Build is the default target.
 
-     The **-v:d** switch specifies a verbose description for the build process.
+     The **-v:d** switch is an abbreviation of **-verbosity:detailed** that you used previously.
 
-     These lines should be displayed:
+    If you already built the output, these lines should be displayed:
 
      **Skipping target "Build" because all output files are up-to-date with respect to the input files.**
 
-     **Input files: HelloWorld.cs**
-
-     **Output files: BinMSBuildSample.exe**
-
      MSBuild skips the Build target because none of the source files have changed since the application was last built.
 
 ## C# example
@@ -399,8 +385,7 @@ The following example shows a project file that compiles a C# application and lo
 ### Code
 
 ```xml
-<Project DefaultTargets = "Compile"
-    xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >
+<Project DefaultTargets = "Compile">
 
     <!-- Set the application name as a property -->
     <PropertyGroup>
@@ -409,11 +394,11 @@ The following example shows a project file that compiles a C# application and lo
 
     <!-- Specify the inputs by type and file name -->
     <ItemGroup>
-        <CSFile Include = "consolehwcs1.cs"/>
+        <CSFile Include = "*.cs"/>
     </ItemGroup>
 
-    <Target Name = "Compile">
-        <!-- Run the Visual C# compilation using input files of type CSFile -->
+    <Target Name="Compile">
+        <!-- Run the C# compilation using input files of type CSFile -->
         <CSC
             Sources = "@(CSFile)"
             OutputAssembly = "$(appname).exe">
@@ -436,8 +421,7 @@ The following example shows a project file that compiles a Visual Basic applicat
 ### Code
 
 ```xml
-<Project DefaultTargets = "Compile"
-    xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >
+<Project DefaultTargets = "Compile">
 
     <!-- Set the application name as a property -->
     <PropertyGroup>

docs/toc.yml

@@ -789,7 +789,7 @@
       href: ide/how-to-configure-projects-to-target-multiple-platforms.md
   - name: MSBuild >>
     href: msbuild/msbuild.md
-  - name: Azure Pipelines and TFS >>
+  - name: Azure Pipelines and Azure DevOps Server >>
     displayName: VSTS Azure DevOps CI/CD Continuous integration delivery
     href: /azure/devops/pipelines/index?view=vsts&preserve-view=true
   - name: Specify build events (Visual Basic)