Merge pull request #10485 from ghogen/refresh-dates

prmerger-automator[bot] · web-flow · commit 49acef830915 · 2022-10-08T00:33:16.000Z
Review and update text and screenshots, if needed
diff --git a/docs/msbuild/customize-your-build.md b/docs/msbuild/customize-your-build.md
@@ -2,7 +2,7 @@
 title: Customize your build | Microsoft Docs
 description: Learn about several extensibility hooks you can use to customize MSBuild projects that use the standard build process. 
 ms.custom: SEO-VS-2020
-ms.date: 09/13/2021
+ms.date: 10/07/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - MSBuild, transforms
diff --git a/docs/msbuild/msbuild.md b/docs/msbuild/msbuild.md
@@ -2,7 +2,7 @@
 title: MSBuild | Microsoft Docs
 description: Learn about how the Microsoft Build Engine (MSBuild) platform provides a project file with an XML schema to control builds.
 ms.custom: SEO-VS-2020
-ms.date: 08/11/2021
+ms.date: 10/07/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - MSBuild, about MSBuild
@@ -17,7 +17,7 @@ ms.workload:
 ---
 # MSBuild
 
-The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild doesn't depend on Visual Studio. By invoking *msbuild.exe* on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.
+The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild doesn't depend on Visual Studio. By invoking *msbuild.exe* or *dotnet build* on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.
 
 Visual Studio uses MSBuild to load and build managed projects. The project files in Visual Studio (*.csproj*, *.vbproj*, *.vcxproj*, and others) contain MSBuild XML code that executes when you build a project by using the IDE. Visual Studio projects import all the necessary settings and build processes to do typical development work, but you can extend or modify them from within Visual Studio or by using an XML editor.
 
@@ -65,11 +65,19 @@ MSBuild.exe MyProj.proj -property:Configuration=Debug
 > [!IMPORTANT]
 > Before you download a project, determine the trustworthiness of the code.
 
+For .NET Core and .NET 5 or later, you typically use `dotnet build` to invoke MSBuild. See [dotnet build](/dotnet/core/tools/dotnet-build).
+
 ## Project file
 
  MSBuild uses an XML-based project file format that's straightforward and extensible. The MSBuild project file format lets developers describe the items that are to be built, and also how they are to be built for different operating systems and configurations. In addition, the project file format lets developers author reusable build rules that can be factored into separate files so that builds can be performed consistently across different projects in the product.
 
- The Visual Studio build system stores project-specific logic in the your project file itself, and uses imported MSBuild XML files with extensions like *.props* and *.targets* to define the standard build logic. The *.props* files define MSBuild properties, and *.targets* files define MSBuild targets. These imports are sometimes visible in the Visual Studio project file, but in newer projects such as .NET Core, .NET 5 and .NET 6 projects, you don't see the imports in the project file; instead, you see an SDK reference. These are called SDK-style projects. When you reference an SDK such as the .NET SDK, the imports of .props and .target files are implicitly specified by the SDK.
+ The Visual Studio build system stores project-specific logic in the your project file itself, and uses imported MSBuild XML files with extensions like `.props` and `.targets` to define the standard build logic. The `.props` files define MSBuild properties, and `.targets` files define MSBuild targets. These imports are sometimes visible in the Visual Studio project file, but in newer projects such as .NET Core, .NET 5 and .NET 6 projects, you don't see the imports in the project file; instead, you see an SDK reference, which looks like this:
+
+```xml
+<Project Sdk="Microsoft.Net.Sdk">
+```
+
+ These are called SDK-style projects. When you reference an SDK such as the .NET SDK, the imports of `.props` and `.target` files are implicitly specified by the SDK.
 
  The following sections describe some of the basic elements of the MSBuild project file format. For a tutorial about how to create a basic project file, see [Walkthrough: Creating an MSBuild project file from scratch](../msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md).
 
diff --git a/docs/msbuild/troubleshooting-dotnet-framework-targeting-errors.md b/docs/msbuild/troubleshooting-dotnet-framework-targeting-errors.md
@@ -2,7 +2,7 @@
 title: Troubleshooting .NET Framework Targeting Errors | Microsoft Docs
 description: Learn about MSBuild errors that might occur because of reference issues and how you can resolve those errors.
 ms.custom: SEO-VS-2020
-ms.date: 06/13/2021
+ms.date: 10/07/2022
 ms.topic: troubleshooting
 f1_keywords:
 - vs.FrameworkTargetingErrors
diff --git a/docs/msbuild/walkthrough-using-msbuild.md b/docs/msbuild/walkthrough-using-msbuild.md
@@ -1,7 +1,7 @@
 ---
 title: Use MSBuild
 description: Learn the various parts of an MSBuild project file, including items, item metadata, properties, targets, and tasks.
-ms.date: 07/28/2021
+ms.date: 10/07/2022
 ms.topic: conceptual
 ms.custom: contperf-fy21q2
 helpviewer_keywords:
@@ -88,17 +88,13 @@ Project files are XML-formatted files with the root node [Project](../msbuild/pr
 <Project ToolsVersion="15.0"  xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
 ```
 
-Newer .NET Core (SDK-style) projects have a `Sdk` attribute.
+Most .NET projects have a `Sdk` attribute. These are called SDK-style projects.
 
 ```xml
 <Project Sdk="Microsoft.NET.Sdk">
 ```
 
-If the project is not an SDK-style project, you must specify the xmlns namespace in the Project element. If `ToolsVersion` is present in a new project, it must match the MSBuild version. If you don't know the MSBuild version, you can get it from the first two numbers from the output of the following command line (for example, 16.0):
-
-```console
-MSBuild -ver
-```
+There are many variations of .NET SDKs for special purposes; they are described at [.NET Project SDKs](/dotnet/core/project-sdk/overview).
 
 The work of building an application is done with [Target](../msbuild/target-element-msbuild.md) and [Task](../msbuild/task-element-msbuild.md) elements.
 
@@ -144,9 +140,9 @@ MSBuild keeps track of the targets of a build, and guarantees that each target i
 
 3. Save the project file.
 
-The Message task is one of the many tasks that ships with MSBuild. For a complete list of available tasks and usage information, see [Task reference](../msbuild/msbuild-task-reference.md).
+The `Message` task is one of the many tasks that ships with MSBuild. For a complete list of available tasks and usage information, see [Task reference](../msbuild/msbuild-task-reference.md).
 
-The Message task takes the string value of the Text attribute as input and displays it on the output device (or writes it to one or more logs, if applicable). The HelloWorld target executes the Message task twice: first to display "Hello", and then to display "World".
+The `Message` task takes the string value of the Text attribute as input and displays it on the output device (or writes it to one or more logs, if applicable). The HelloWorld target executes the Message task twice: first to display "Hello", and then to display "World".
 
 ## Build the target
 
@@ -161,7 +157,7 @@ Run MSBuild from the **Developer Command Prompt** for Visual Studio to build the
 
 1. Open the **Command Window**.
 
-   (Windows 10) In the search box on the taskbar, start typing the name of the tool, such as `dev` or `developer command prompt`. This brings up a list of installed apps that match your search pattern.
+   In the search box on the taskbar, start typing the name of the tool, such as `dev` or `developer command prompt`. This brings up a list of installed apps that match your search pattern.
 
    If you need to find it manually, the file is *LaunchDevCmd.bat* in the *<visualstudio installation folder\>\Common7\Tools* folder.
 
@@ -350,7 +346,7 @@ All items are child elements of ItemGroup elements. The item name is the name of
 
 defines an item group containing two items. The item type Compile has two values: *Program.cs* and *Properties\AssemblyInfo.cs*.
 
-The following code creates the same item type by declaring both files in one Include attribute, separated by a semicolon.
+The following code creates the same item type by declaring both files in one `Include` attribute, separated by a semicolon.
 
 ```xml
 <ItemGroup>
@@ -365,13 +361,13 @@ For more information, see [Items](../msbuild/msbuild-items.md).
 
 ## Examine item type values
 
- To get the values of an item type, use the following syntax, where ItemType is the name of the item type:
+ To get the values of an item type, use the following syntax, where `ItemType` is the name of the item type:
 
 ```xml
 @(ItemType)
 ```
 
-Use this syntax to examine the Compile item type in the project file.
+Use this syntax to examine the `Compile` item type in the project file.
 
 **To examine item type values:**
 
@@ -393,7 +389,7 @@ Use this syntax to examine the Compile item type in the project file.
 
 1. Examine the output. You should see this long line:
 
-    ```
+    ```output
     Compile item type contains Form1.cs;Form1.Designer.cs;Program.cs;Properties\AssemblyInfo.cs;Properties\Resources.Designer.cs;Properties\Settings.Designer.cs
     ```
 
@@ -425,7 +421,7 @@ Change the Message task to use carriage returns and line feeds (%0A%0D) to displ
 
 4. Examine the output. You should see these lines:
 
-    ```
+    ```output
     Compile item type contains Form1.cs
     Form1.Designer.cs
     Program.cs
@@ -506,7 +502,7 @@ would not exclude the file *Form1.cs*, which was added in the preceding item ele
 
 5. Examine the output. You should see this line:
 
-    ```
+    ```output
     XFiles item type contains Form1.cs;Program.cs;Properties/Resources.resx
     ```
 
@@ -524,7 +520,7 @@ would not exclude the file *Form1.cs*, which was added in the preceding item ele
 </ItemGroup>
 ```
 
- To get the metadata value of an item type, use the following syntax, where ItemType is the name of the item type and MetaDataName is the name of the metadata:
+ To get the metadata value of an item type, use the following syntax, where `ItemType` is the name of the item type and MetaDataName is the name of the metadata:
 
 ```xml
 %(ItemType.MetaDataName)
@@ -626,7 +622,9 @@ Notice that metadata expressed in this syntax does not cause batching.
 
 ## Next steps
 
- To learn how to create a simple project file one step at a time, try out the [Walkthrough: Creating an MSBuild project file from scratch](../msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md).
+ To learn how to create a simple project file one step at a time, on Windows, try out the [Walkthrough: Creating an MSBuild project file from scratch](../msbuild/walkthrough-creating-an-msbuild-project-file-from-scratch.md).
+
+If you're primarily using the .NET SDK, you may wish to continue reading at [MSBuild Reference for .NET SDK Projects](/dotnet/core/project-sdk/msbuild-props).
 
 ## See also
 
