Merge pull request #13829 from GitHubber17/415544-h

410544 - MSBuild error article updates

Author: JillGrant615

docs/msbuild/errors/msb6011.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB6011"
-description: "Invalid parameters passed to the 'task-name' task."
-ms.date: "07/07/2021"
+title: MSB6011 diagnostic code
+description: Learn about the possible causes of the MSB6011 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB6011
@@ -16,8 +16,24 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB6011: Invalid parameters passed to the 'task-name' task
+# MSB6011
 
-This error occurs when a task indicates that the parameters passed to it are not valid. Normally, a task generates a customized error message in that case, by specifying such in the implementation of the `ValidateParameters` method. If the task doesn't override that method, the base ToolTask version of that method is used, which generates this error.
+This article describes the MSB6011 error code.
 
-If the task is provided by a vendor, consider contacting the vendor and asking them to implement the `ValidateParameters` method on the task. If this is your own custom task, consider implementing that method to provide a detailed message that indicates what parameter was invalid and why.
+## Message text
+
+`MSB6011: Invalid parameters passed to the 'task-name' task.`
+
+## Description
+
+This error occurs when a task indicates that the parameters passed to it are invalid. In most cases, a task generates a customized error message by specifying such in the implementation of the `ValidateParameters` method. If the task doesn't override the `ValidateParameters` method, the base ToolTask version of that method is used, which generates the error.
+
+## Resolution
+
+If the task is provided by a vendor, you might contact the vendor and ask them to implement the `ValidateParameters` method on the task.
+
+If the implementation uses your own custom task, consider implementing the `ValidateParameters` method to provide a detailed message that identifies the invalid parameter and reason.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8003.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8003"
-description: "MSBuild warning MSB8003 occurs when a build property isn't defined. Some build tools may not be found."
-ms.date: 10/29/2021
+title: MSB8003 diagnostic code
+description: Learn about the possible causes of the MSB8003 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8003
@@ -12,12 +12,32 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8003
+# MSB8003
 
-> MSB8003: The *property-name* property is not defined. Some build tools may not be found.
+This article describes the MSB8003 error code.
 
-To resolve this issue, define a supported value for the specified property.
+## Message text
 
-This error can occur when the `VCToolsInstallDir` property hasn't been set. This error may occur if you haven't installed a C++ workload in the Visual Studio Installer. You can use the Visual Studio Installer to install workloads and optional components. For more information, see [Modify Visual Studio](../../install/modify-visual-studio.md). Choose one of the C++ workloads to install the C/C++ toolset. Use the **Individual components** tab in the installer to choose specific platforms, libraries, and SDKs.
+`MSB8003: The *property-name* property is not defined. Some build tools may not be found.`
 
-This error can also occur when the `WindowsSDKDir` property hasn't been set in your project. Since Visual Studio 2015, the Windows SDK hosts the headers and libraries for the C runtime library. We recommend you install and use the latest available Windows SDK in the Visual Studio Installer, and set the **Windows SDK Version** property in your project property pages to match.
+## Description
+
+This error occurs when a build property isn't defined.
+
+Common causes for this error include:
+
+- The `VCToolsInstallDir` property isn't set.
+- The `WindowsSDKDir` property isn't set in your project.
+- A C++ workload isn't installed with the Visual Studio Installer. 
+
+## Resolution
+
+Define a supported value for the specified property, such as the `VCToolsInstallDir` or `WindowsSDKDir` property.
+
+Use the Visual Studio Installer to install workloads and optional components. For more information, see [Modify Visual Studio](../../install/modify-visual-studio.md). Choose one of the C++ workloads and install the C/C++ toolset. Use the **Individual components** tab in the installer to choose specific platforms, libraries, and SDKs.
+
+Since Visual Studio 2015, the Windows SDK hosts the headers and libraries for the C runtime library. We recommend you install and use the latest available Windows SDK in the Visual Studio Installer, and set the **Windows SDK Version** property in your project property pages to match.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8004.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8004"
-description: "MSBuild warning MSB8004 occurs when an intermediate or output directory doesn't end with a trailing slash."
-ms.date: 10/29/2021
+title: MSB8004 diagnostic code
+description: Learn about the possible causes of the MSB8004 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8004
@@ -12,10 +12,22 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8004
+# MSB8004
 
-> MSB8004: *property* Directory does not end with a trailing slash. This build instance will add the slash as it is required to allow proper evaluation of the *property* Directory.
+This article describes the MSB8004 error code.
 
-This error can occur when your configuration doesn't include the trailing slash on an Intermediate or Output directory path.
+## Message text
 
-To resolve this issue, add a trailing slash to the specified path in your configuration. You can set the **Output Directory** and **Intermediate Directory** properties for these paths in your project properties. For more information, see [General Property Page (Project)](/cpp/build/reference/general-property-page-project).
+`MSB8004: *property* Directory does not end with a trailing slash. This build instance will add the slash as it is required to allow proper evaluation of the *property* Directory.`
+
+## Description
+
+This error occurs when an intermediate or output directory doesn't end with a trailing forward slash.
+
+## Resolution
+
+Add a trailing forward slash (`\`) to the specified path in your configuration. You can set the **Output Directory** and **Intermediate Directory** properties for these paths in your project properties. For more information, see [General property page (project)](/cpp/build/reference/general-property-page-project).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8005.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild warning MSB8005"
-description: "MSBuild warning MSB8005 occurs when a specified NMake build property in a makefile project doesn't exist."
-ms.date: 10/29/2021
+title: MSB8005 diagnostic code
+description: Learn about the possible causes of the MSB8005 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8005
@@ -12,10 +12,24 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild warning MSB8005
+# MSB8005
 
-> MSB8005: The property '*property-name*' doesn't exist.  Skipping...
+This article describes the MSB8005 error code.
 
-This error can occur when using a makefile to build a project, and you haven't set the project properties **Build Command Line**, **Clean Command Line**, or **Rebuild All Command Line**.
+## Message text
 
-To resolve this issue, add the specified build command lines to your project properties. For more information, see [NMake Property Page](/cpp/build/reference/nmake-property-page).
+`MSB8005: The property '*property-name*' doesn't exist.  Skipping...`
+
+## Description
+
+This error occurs when a specified NMake build property in a makefile project doesn't exist.
+
+The problem can occur when you use a makefile to build a project, and you don't set the project properties **Build Command Line**, **Clean Command Line**, or **Rebuild All Command Line**.
+
+## Resolution
+
+Add the specified build command lines to your project properties. For more information, see [NMake property page](/cpp/build/reference/nmake-property-page).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8006.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8006"
-description: "MSBuild error MSB8006 occurs when the platform for your project is invalid."
-ms.date: 05/27/2021
+title: MSB8006 diagnostic code
+description: Learn about the possible causes of the MSB8006 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8006
@@ -12,16 +12,30 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8006
+# MSB8006
 
-> The Platform for project '*project-name.vcxproj*' is invalid.  Platform='*platform-name*'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Platform.
+This article describes the MSB8006 error code.
+
+## Message text
+
+`MSB8006: The Platform for project '*project-name.vcxproj*' is invalid.  Platform='*platform-name*'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Platform.`
+
+## Description
+
+This error occurs when the platform for your project is invalid.
 
 A *Platform* is a build target architecture that uses a matching set of C++ build tools and libraries, or *toolset*. Visual Studio supplies specific platform toolsets to build for Win32 (x86), x64, ARM, and ARM64 Windows targets. It also supports optional platform toolsets to build for Linux, Android, and iOS targets.
 
-There are several ways to resolve this issue:
+This error can occur when your project specifies a platform, but it's not the one installed with Visual Studio, or Visual Studio can't find it.  
+
+## Resolution
+
+Use the Visual Studio Installer to install optional platforms and toolsets. For more information, see [Modify Visual Studio](../../install/modify-visual-studio.md). Use the **Individual components** tab in the installer to choose specific platforms, libraries, and SDKs.
+
+Most projects don't need to specify a custom platform, but it's possible to create one. For more information, see [Visual Studio C++ Project system extensibility and toolset integration](../../extensibility/visual-cpp-project-extensibility.md). After you create the custom *`.props`* and *`.targets`* files for your platform, you can select it in the IDE in the **Property Pages** dialog for your project. 
 
-- This error can occur when your project has specified a platform, but it's not one that Visual Studio has installed. You can use the Visual Studio Installer to install optional platforms and toolsets. For more information, see [Modify Visual Studio](../../install/modify-visual-studio.md). Use the **Individual components** tab in the installer to choose specific platforms, libraries, and SDKs.
+Make sure your project is loaded when its built by a referencing project. Verify your project is built for the same platform as the referencing project.
 
-- You've specified a custom platform, but Visual Studio can't find it. Most projects don't need to specify a custom platform, but it's possible to create one. For more information, see [Visual Studio C++ Project system extensibility and toolset integration](../../extensibility/visual-cpp-project-extensibility.md). Once you've created the custom *`.props`* and *`.targets`* files for your platform, you can select it in the IDE in the Property Pages dialog for your project. 
+## Applies to
 
-- Make sure that the project is loaded when built by a referencing project. Verify that it's built for the same platform as the referencing project.
+All versions of MSBuild

docs/msbuild/errors/msb8007.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8007"
-description: "MSBuild error MSB8007 occurs when the target platform build property doesn't exist or isn't valid."
-ms.date: 10/29/2021
+title: MSB8007 diagnostic code
+description: Learn about the possible causes of the MSB8007 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8007
@@ -12,8 +12,22 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8007
+# MSB8007
 
-> MSB8007: The Platform for project '*project-name*' is invalid.  Platform='*platform-name*'. You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Platform that doesn't exist for this project.
+This article describes the MSB8007 error code.
 
-To resolve this issue, change the **Target Platform** property for your project to a valid value. For more information, see [General Property Page (Project)](/cpp/build/reference/general-property-page-project).
+## Message text
+
+`MSB8007: The Platform for project '*project-name*' is invalid.  Platform='*platform-name*'. You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Platform that doesn't exist for this project.`
+
+## Description
+
+This error occurs when the target platform build property doesn't exist or isn't valid.
+
+## Resolution
+
+Change the **Target Platform** property for your project to a valid value. For more information, see [General property page (project)](/cpp/build/reference/general-property-page-project).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8010.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8010"
-description: "MSBuild error MSB8010 occurs when the v90 platform toolset from Visual Studio 2008 isn't installed."
-ms.date: 10/29/2021
+title: MSB8010 diagnostic code
+description: Learn about the possible causes of the MSB8010 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8010
@@ -12,8 +12,22 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8010
+# MSB8010
 
-> MSB8010: Specified platform toolset (v90) requires Visual Studio 2008. Please make sure that Visual Studio 2008 is installed on the machine.
+This article describes the MSB8010 error code.
 
-To resolve this issue, install Visual Studio 2008 to make the v90 platform toolset available. For more information, see [Visual Studio 2008](https://www.microsoft.com/download/details.aspx?id=7873) in the Microsoft Download Center.
+## Message text
+
+`MSB8010: Specified platform toolset (v90) requires Visual Studio 2008. Please make sure that Visual Studio 2008 is installed on the machine.`
+
+## Description
+
+This error occurs when the v90 platform toolset from Visual Studio 2008 isn't installed.
+
+## Resolution
+
+Install Visual Studio 2008 to make the v90 platform toolset available. For more information, see [Visual Studio 2008](https://www.microsoft.com/download/details.aspx?id=7873) in the Microsoft Download Center.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb8011.md

@@ -1,7 +1,7 @@
 ---
-title: "MSBuild error MSB8011"
-description: "MSBuild error MSB8011 occurs when a component registration operation fails during the build."
-ms.date: 10/29/2021
+title: MSB8011 diagnostic code
+description: Learn about the possible causes of the MSB8011 build error and get troubleshooting tips.
+ms.date: 04/16/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB8011
@@ -12,16 +12,33 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSBuild error MSB8011
+# MSB8011
 
-> MSB8011: Failed to register output. Please try enabling Per-user Redirection or register the component from a command prompt with elevated permissions.
+This article describes the MSB8011 error code.
 
-This error occurs when an attempt to register a component fails. A registration failure can occur for several reasons. 
+## Message text
 
-- Different permissions may be required for per-user or global registration. The IDE, developer command prompt, or *`regsvr32.exe`* process may need to run with elevated permissions (Run as Administrator). 
+`MSB8011: Failed to register output. Please try enabling Per-user Redirection or register the component from a command prompt with elevated permissions.`
 
-- Component registration may fail because required DLL dependencies couldn't be found. You may need to place dependencies in the same directory as the component to register.
+## Description
 
-- Component registration may fail because required DLL dependencies don't match the target architecture of the component. Make sure to use dependencies built for the same architecture as your component.
+This error occurs when an attempt to register a component fails during the build.
 
-- Component registration may fail if your component requires but doesn't define a `DllInstall` entry point. 
+A registration failure can occur for several reasons:
+
+- Different permissions might be required for per-user or global registration, including elevated permissions. 
+- Required DLL dependencies can't be found.
+- Required DLL dependencies don't match the target architecture of the component. 
+- Required `DllInstall` entry point isn't defined. 
+
+## Resolution
+
+Try running the IDE, developer command prompt, or the *`regsvr32.exe`* process with elevated permissions (Run as Administrator). 
+
+Make sure to use dependencies built for the same architecture as your component. Place dependencies in the same directory as the component to enable registration. 
+
+If your component requires a`DllInstall` entry point, make sure the entry point is defined. 
+
+## Applies to
+
+All versions of MSBuild