Merge pull request #13830 from GitHubber17/415544-i

410544 - MSBuild error article updates

Author: JillGrant615

docs/msbuild/errors/msb8024.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8024"
-description: "MSBuild error MSB8024 occurs when the project can't use the static C++ runtime library."
-ms.date: 10/29/2021
+title: MSB8024 diagnostic code
+description: Learn about the possible causes of the MSB8024 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8024
@@ -12,10 +12,22 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8024
+# MSB8024
 
-> MSB8024: Using static version of the C++ runtime library is not supported.
+This article describes the MSB8024 error code.
 
-When you specify the **`/MT`** or **`/MTd`** (Use multithreaded runtime library) linker options, you must use the dynamic library version of the Universal C Runtime Library (UCRT). 
+## Message text
 
-To resolve this issue, modify the project to use the dynamic UCRT library. For more information, see [Upgrade your code to the Universal CRT](/cpp/porting/upgrade-your-code-to-the-universal-crt).
+`MSB8024: Using static version of the C++ runtime library is not supported.`
+
+## Description
+
+This error occurs when the project can't use the static C++ runtime library. When you specify the **`/MT`** or **`/MTd`** (to use multithreaded runtime library) linker options, you must use the dynamic library version of the Universal C Runtime Library (UCRT). 
+
+## Resolution
+
+Modify the project to use the dynamic UCRT library. For more information, see [Upgrade your code to the Universal CRT](/cpp/porting/upgrade-your-code-to-the-universal-crt).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8027.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8027"
-description: "MSBuild warning MSB8027 occurs when two or more source files in your project have the same name."
-ms.date: 05/27/2021
+title: MSB8027 diagnostic code
+description: Learn about the possible causes of the MSB8027 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8027
@@ -12,14 +12,33 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8027
+# MSB8027
 
-> Two or more files with the name of *filename* will produce outputs to the same location. This can lead to an incorrect build result. The files involved are *file-path-1* *file-path-2*.
+This article describes the MSB8027 error code.
 
-Two or more source files have the same name, and build results go to the same intermediate directory. The output of the file built first gets overwritten by the next file with the same name. The error is often followed by a `LNK4042` warning. This error can occur when you've combined projects that use the same filename in different locations.
+## Message text
 
-There are several ways to resolve this issue:
+`MSB8027: Two or more files with the name of *filename* will produce outputs to the same location. This can lead to an incorrect build result. The files involved are *file-path-1* *file-path-2*.`
 
-- If your project has two or more source files that have the same name, give the files unique names.
+## Description
 
-- If you can't change the file names, compile each file to a unique intermediate directory. To set the intermediate file location, select the source file in Solution Explorer, then right-click to open the shortcut menu. Choose **Properties** to open the **Property Pages** dialog for the source file. Select the **Configuration Properties** > **C/C++** > **Output Files** property page. Change the **Object File Name** property from `$(IntDir)` to `$(IntDir)%(RelativeDir)`. Choose **OK** to save your changes. 
+This error occurs when two or more source files have the same name, and build results go to the same intermediate directory. After the first file builds, the build overwrites output from the first file with output from the next file that has the same name.
+
+The error output message is often followed by a `LNK4042` warning. This error can occur when you combine projects that use the same filename in different locations.
+
+## Resolution
+
+If your project has two or more source files that have the same name, give each file a unique name.
+
+If you can't change the file names, compile each file to a unique intermediate directory.
+
+To set the intermediate file location, follow these steps:
+
+1. In **Solution Explorer**, right-click the source file, and select **Properties**.
+1. In the **Property Pages** dialog for the source file, select the **Configuration Properties** > **C/C++** > **Output Files** property page.
+1. Change the **Object File Name** property from `$(IntDir)` to `$(IntDir)%(RelativeDir)`.
+1. Select **OK** to save your changes. 
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8028.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8028"
-description: "MSBuild warning MSB8028 occurs when two or more projects share outputs in the same intermediate directories."
-ms.date: 11/01/2021
+title: MSB8028 diagnostic code
+description: Learn about the possible causes of the MSB8028 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8028
@@ -12,14 +12,31 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8028
+# MSB8028
 
-> MSB8028: The intermediate directory (*shared-intermediate-path*) contains files shared from another project (*intermediate-path*). This can lead to incorrect clean and rebuild behavior.
+This article describes the MSB8028 error code.
 
-Two or more projects produce outputs to the same location. This issue can lead to an incorrect build result. The intermediate directories involved are *shared-intermediate-path* and *intermediate-path*.
+## Message text
 
-To resolve this issue:
+`MSB8028: The intermediate directory (*shared-intermediate-path*) contains files shared from another project (*intermediate-path*). This can lead to incorrect clean and rebuild behavior.`
 
-- For each project in your solution, set your `$(IntDir)` property for each supported configuration and platform to use its own unique directory. To set the intermediate file location, select the project in Solution Explorer, then right-click to open the shortcut menu. Choose **Properties** to open the **Property Pages** dialog for the project. Select the **Configuration Properties** > **C/C++** > **Output Files** property page. For each configuration in the project, set the **Intermediate Directory** property.
+## Description
 
-Note that `$(IntDir)` is an MSBuild property (macro) that applies to C++ build. See [Common macros for MSBuild commands and properties](/cpp/build/reference/common-macros-for-build-commands-and-properties).
+This error occurs when two or more projects produce outputs to the same location. This issue can lead to an incorrect build result. The intermediate directories involved are *shared-intermediate-path* and *intermediate-path*.
+
+## Resolution
+
+For each project in your solution, set your `$(IntDir)` property for each supported configuration and platform, so it uses its own unique directory.
+
+To set the intermediate file location, follow these steps:
+
+1. In **Solution Explorer**, right-click the project node, and select **Properties**.
+1. In the **Property Pages** dialog for the project, select the **Configuration Properties** > **C/C++** > **Output Files** property page.
+1. For each configuration in the project, set the **Intermediate Directory** property.
+1. Select **OK** to save your changes.
+
+Keep in mind that `$(IntDir)` is an MSBuild property (macro) that applies to the C++ build process. For more information, see [Common macros for MSBuild commands and properties](/cpp/build/reference/common-macros-for-build-commands-and-properties).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8029.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8029"
-description: "MSBuild warning MSB8029 occurs when intermediate or output directories are under the Temporary directory."
-ms.date: 11/01/2021
+title: MSB8029 diagnostic code
+description: Learn about the possible causes of the MSB8029 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8029
@@ -12,10 +12,29 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8029
+# MSB8029
 
-> MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build.
+This article describes the MSB8029 error code.
 
-To resolve this issue:
+## Message text
 
-- For each project in your solution, set your intermediate and output build directory properties for each supported configuration and platform to use a directory that's not under the Temporary directory.  To set the directories, select the project in Solution Explorer, then right-click to open the shortcut menu. Choose **Properties** to open the **Property Pages** dialog for the project. Select the **Configuration Properties** > **C/C++** > **Output Files** property page. For each configuration in the project, set the **Intermediate Directory** and **Output Directory** property.
+`MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build.`
+
+## Description
+
+This error occurs when the intermediate directory and output directory are located in the *Temporary* directory.
+
+## Resolution
+
+For each project in your solution, set your intermediate and output build directory properties for each supported configuration and platform to use a directory that's not under the *Temporary* directory.
+
+To set the locations for the two directories, follow these steps:
+
+1. In **Solution Explorer**, right-click the project node, and select **Properties**.
+1. In the **Property Pages** dialog for the project, select the **Configuration Properties** > **C/C++** > **Output Files** property page.
+1. For each configuration in the project, set the **Intermediate Directory** property and the **Output Directory** property.
+1. Select **OK** to save your changes.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8036.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8036"
-description: "MSBuild error MSB8036 occurs when Visual Studio or MSBuild can't find the Windows SDK requested by your project in the expected location."
-ms.date: "02/10/2021"
+title: MSB8036 diagnostic code
+description: Learn about the possible causes of the MSB8036 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8036
@@ -12,28 +12,53 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8036
+# MSB8036
 
-> The Windows SDK '*version*' was not found
+This article describes the MSB8036 error code.
+
+## Message text
+
+`MSB8036: The Windows SDK *version* was not found.`
+
+## Description
 
 This error occurs when Visual Studio or MSBuild can't find the Windows SDK requested by your project in the expected location.
 
-## Windows SDK version specified in project
+## Resolution
+
+The following sections describe options for resolving the MSB8036 error based on your configuration.
+
+### Specify Windows SDK version for project in Visual Studio
+
+If you build your project in Visual Studio, confirm the project targets the correct version of the Windows SDK:
 
-If you're building your project in Visual Studio, the first thing to check is that the project targets the correct version of the Windows SDK. Right-click on the project node, and choose **Properties** or press **Alt**+**Enter**. The Property Pages dialog for your project appears. Under **Configuration Properties** > **General**, look for **Windows SDK Version**. For example, it might be **10 (latest installed version)**, which selects the most recent version if more than one version is installed. If you select the dropdown, you can see specific versions that Visual Studio has detected. Make sure that the version your project needs is selected.
+1. In **Solution Explorer**, right-click the project node, and select **Properties** (**Alt**+**Enter**).
+1. In the **Property Pages** dialog for your project, select the **Configuration Properties** > **General** property page.
+1. Check the value for the **Windows SDK Version** property.
 
-If you're using MSBuild directly, not with Visual Studio, you should check the places where the `WindowsTargetPlatformVersion` property might be set. It's usually in the project file, but it could also be in an imported file or in a global settings file such as *Directory.build.props*. This file can be located anywhere in the parent path to your project, up to the root of the drive. The default setting in a newly created project file looks like this:
+   The dropdown list of values shows the specific versions detected by Visual Studio. The value **10.0 (latest installed version)** instructs Visual Studio to always use the most recent SDK version, if multiple versions are installed.
+
+1. Use the dropdown list to select the SDK version your project requires.
+1. Select **OK** to save your changes.
+
+### Use MSBuild directly without Visual Studio
+
+If you use MSBuild directly without Visual Studio, check any place where the `WindowsTargetPlatformVersion` property might be set. The property is often set in the project file, but it might also be defined in an imported file or in a global settings file like *Directory.build.props*. The `.props` file can be located anywhere in the parent path to your project, up to the root of the drive. The following XML shows the default setting in a newly created project file:
 
 ```xml
 <WindowsTargetPlatformVersion>10.0</WindowsTargetPlatformVersion>
 ```
 
 Also, check build scripts or CI jobs that invoke MSBuild. Make sure the command line isn't passing an invalid value for this property.
 
-## Install or reinstall the Windows SDK
+### Install or reinstall the Windows SDK
+
+If the previous options don't resolve the issue, install or reinstall the Windows SDK version your project needs.
+
+You can install specific versions of the Windows SDK in the Visual Studio Installer by selecting the version in **Individual Components**. You can also download the Windows SDK from the [Windows Dev Center](https://developer.microsoft.com/windows/downloads/windows-sdk/).
 
-If that doesn't resolve the issue, install or reinstall the Windows SDK version your project needs. You can install specific versions of the Windows SDK by using the Visual Studio Installer. Select the version in **Individual Components**. You can also download the Windows SDK from the [Windows Dev Center](https://developer.microsoft.com/windows/downloads/windows-sdk/).
+For more information, see [Use the Windows 10 SDK in a Windows Desktop application](/cpp/windows/how-to-use-the-windows-10-sdk-in-a-windows-desktop-application).
 
-## See also
+## Applies to
 
-- [How to: Use the Windows 10 SDK in a Windows Desktop application](/cpp/windows/how-to-use-the-windows-10-sdk-in-a-windows-desktop-application)
+All versions of MSBuild