update articles for collection consistency (#13817)

GitHubber17 · web-flow · commit 36b234f1a79f · 2025-04-14T09:17:24.000-07:00
diff --git a/docs/msbuild/errors/msb3021.md b/docs/msbuild/errors/msb3021.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3021: Unable to copy file 'source' to 'destination'."
-description: "This error occurs when an error occurred when trying to copy a file."
-ms.date: "08/15/2022"
+title: MSB3021 diagnostic code
+description: Learn about the possible causes of the MSB3021 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3021
@@ -18,12 +18,22 @@ ms.subservice: msbuild
 ---
 # MSB3021
 
+This article describes the MSB3021 error code.
+
+## Message text
+
+`Unable to copy file 'source' to 'destination'.`
+
+## Description
+
 This diagnostic code is emitted when an error occurs when trying to copy a file. The error text from the operating system is displayed, which usually provides specific information about the failure.
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
+
+Common causes include the file is locked by another process, insufficient permissions to write to the destination folder, insufficient space on the drive, and so on. Make sure the file is not in use, that MSBuild has write permissions on the destination folder, and that there is sufficient space on the disk.
 
-```output
-MSB3021: Unable to copy file 'source' to 'destination'.
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem. Common causes include the file is locked by another process, insufficient permissions to write to the destination folder, insufficient space on the drive, and so on. Make sure the file is not in use, that MSBuild has write permissions on the destination folder, and that there is sufficient space on the disk.
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3026.md b/docs/msbuild/errors/msb3026.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3026: Could not copy 'source' to 'destination'. Beginning retry 'count' in 'milliseconds'."
-description: "This diagnostic code is emitted when MSBuild tries multiple times to copy a file."
-ms.date: "08/15/2022"
+title: MSB3026 diagnostic code
+description: Learn about the possible causes of the MSB3026 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3026
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3026
 
+This article describes the MSB3026 error code.
+
+## Message text
+
+`Could not copy 'source' to 'destination'. Beginning retry 'count' in 'milliseconds'.`
+
+## Description 
+
 This diagnostic code is emitted when MSBuild tries multiple times to copy a file.
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
 
-```output
-MSB3026: Could not copy 'source' to 'destination'. Beginning retry 'count' in 'milliseconds'.
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem.
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3027.md b/docs/msbuild/errors/msb3027.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3027: Could not copy 'source' to 'destination'. Exceeded retry count of 'number'. Failed."
-description: "This error occurs when MSBuild tries to copy a file repeatedly and fails when the limit of the number of retries is reached."
-ms.date: "07/07/2021"
+title: MSB3027 diagnostic code
+description: Learn about the possible causes of the MSB3027 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3027
@@ -16,8 +16,24 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3027: Could not copy 'source' to 'dest'. Exceeded retry count of 'number'. Failed
+# MSB3027
 
-This error occurs when MSBuild tries to copy a file repeatedly and fails when the limit of the number of retries is reached. Look to the additional error text for any error from the operating system that indicates what the problem might be.
+This article describes the MSB3027 error code.
+
+## Message text
+
+`Could not copy 'source' to 'dest'. Exceeded retry count of 'number'. Failed`
+
+## Description
+
+This error occurs when MSBuild tries to copy a file repeatedly and fails when the limit of the number of retries is reached.
+
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
 
 Typical causes include the destination file is in use by another program, the permissions to not allow writing to the destination file, not enough space on the drive, or the network drive is not available due to a network or permissions error.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3030.md b/docs/msbuild/errors/msb3030.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3030: Could not copy the file 'file' because it was not found."
-description: "This error occurs when a file that was supposed to be copied isn't found at the expected location."
-ms.date: "08/15/2022"
+title: MSB3030 diagnostic code
+description: Learn about the possible causes of the MSB3030 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3030
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3030
 
-This error occurs when a file that was supposed to be copied isn't found at the expected location.
+This article describes the MSB3030 error code.
+
+## Message text
 
-The full message resembles the following text:
+`Could not copy the file 'file' because it was not found.`
 
-```output
-MSB3030: Could not copy the file 'file' because it was not found.
-```
+## Description
+
+This error occurs when a file that was supposed to be copied isn't found at the expected location.
+
+## Resolution
 
 Check that the path is correct, and that the file exists on disk.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3041.md b/docs/msbuild/errors/msb3041.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3041: Unable to create a manifest resource name for 'resource'."
-description: "This error occurs when MSBuild is unable to create a manifest resource name for the specified resource."
-ms.date: "08/15/2022"
+title: MSB3041 diagnostic code
+description: Learn about the possible causes of the MSB3041 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3041
@@ -18,13 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3041
 
+This article describes the MSB3041 error code.
+
+## Message text
+
+`Unable to create a manifest resource name for 'resource'.`
+
+## Description
+
 This error occurs when a manifest resource name could not be created for the specified resource. 
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
 
-```output
-MSB3041: Unable to create a manifest resource name for 'resource'.
-```
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
 
-Look to the additional information for the cause of the failure.
+## Applies to
 
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3061.md b/docs/msbuild/errors/msb3061.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3061: Unable to delete file 'filename'."
-description: "This error occurs when MSBuild attempts to delete a file and an operating system error occurs."
-ms.date: "08/15/2022"
+title: MSB3061 diagnostic code
+description: Learn about the possible causes of the MSB3061 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3061
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3061
 
-This diagnostic code is emitted when MSBuild tried to delete a file, but an error occurred and the file couldn't be deleted.
+This article describes the MSB3061 error code.
+
+## Message text
 
-The full message is something like:
+`Unable to delete file 'filename'.`
 
-```output
-MSB3061: Unable to delete file 'filename'.
-```
+## Description
+
+This diagnostic code is emitted when MSBuild tried to delete a file, but an error occurred and the file couldn't be deleted.
+
+## Resolution
 
 Check that the file exists and is at the expected location, MSBuild has write permissions to the file and folder, the file isn't being used by another process, and that isn't a read-only file.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3073.md b/docs/msbuild/errors/msb3073.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3073: The command 'command' exited with code 'return code'. "
-description: "This error occurs when a command exists with an error condition."
-ms.date: "08/15/2024"
+title: MSB3073 diagnostic code
+description: Learn about the possible causes of the MSB3073 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3073
@@ -18,20 +18,28 @@ ms.subservice: msbuild
 ---
 # MSB3073
 
-This diagnostic code is emitted when an executable exited with an error code, or emitted an error in the expected format. Specifically, the MSBuild [Exec task](../exec-task.md) encountered an error condition in the executable it was trying to run.
+This article describes the MSB3073 error code.
+
+## Message text
 
-The complete message is something like this:
+`The command 'command' exited with code 'return code'.`
 
-```output
-MSB3073: The command 'command' exited with code 'return code'.
-```
+## Description
+
+This diagnostic code is emitted when an executable exited with an error code, or emitted an error in the expected format. Specifically, the MSBuild [Exec task](../exec-task.md) encountered an error condition in the executable it was trying to run.
 
 The meaning of the return code is specific to the executable that was being run. Refer to the documentation for the tool for the interpretation of a non-zero exit code. If you get this error and the exit code is zero, it's because the output contained text that was interpreted as an error because the `Exec` task was invoked with the `CustomErrorRegularExpression` set to a string that matched something in the tool's output.
 
+## Resolution
+
 Look to the output of the command to determine the root cause of the failure. If logging was enabled in the build, the output might be written to the build log.
 
 To diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
 
 You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
 
 It might be helpful to reproduce the error in isolation. Try running the tool separately with the same inputs and command-line arguments that MSBuild used in the build. If symbols are available and you have a Debug build of the tool, you can try attaching a debugger to the tool and debug the tool itself to see what the problem is.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3075.md b/docs/msbuild/errors/msb3075.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3075: The command 'name' exited with code 'error-code'."
-description: "This error occurs when MSBuild isn't running with sufficient privileges to run a particular command."
-ms.date: "06/18/2021"
+title: MSB3075 diagnostic code
+description: Learn about the possible causes of the MSB3075 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3075
@@ -16,12 +16,26 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3075: The command 'name' exited with code 'error-code'. Please verify that you have sufficient rights to run this command
+# MSB3075
+
+This article describes the MSB3075 error code.
+
+## Message text
+
+`The command 'name' exited with code 'error-code'. Please verify that you have sufficient rights to run this command`
+
+## Description
 
 This error occurs when MSBuild isn't running with sufficient privileges to run a particular command.
 
+## Resolution
+
 You might be tempted to run MSBuild or Visual Studio as Administrator to resolve the issue, but that isn't usually necessary.
 
 Check the executable listed in the error message and make sure it allows execute permissions.
 
 The error can occur in projects that write to the registry, which usually requires elevated privileges. If you are building a C++ project, enabling [Per-user Redirection](/cpp/build/reference/linker-property-pages#per-user-redirection) in the Linker settings might solve the issue.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3086.md b/docs/msbuild/errors/msb3086.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3086"
-description: "Task could not find  'tool' using the SdkToolsPath 'path' or the registry key 'key'. Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed"
-ms.date: "07/07/2021"
+title: MSB3086 diagnostic code
+description: Learn about the possible causes of the MSB3086 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3086
@@ -18,10 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3086
 
-The full error text is similar to the following example:
+This article describes the MSB3086 error code.
 
-```output
-MSB3086: Task could not find 'tool' using the SdkToolsPath 'path' or the registry key 'key'. Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed
-```
+## Message text
 
-This error occurs when a tool could not be found on the paths searched. Try reinstalling the Windows SDK.
+`Task could not find 'tool' using the SdkToolsPath 'path' or the registry key 'key'. Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed`
+
+## Description
+
+This error occurs when a tool could not be found on the paths searched. 
+
+## Resolution
+
+Try reinstalling the Windows SDK.
+
+## Applies to
+
+All versions of MSBuild
diff --git a/docs/msbuild/errors/msb3101.md b/docs/msbuild/errors/msb3101.md
@@ -1,7 +1,7 @@
 ---
-title: "MSB3101: Could not write state file 'filename'."
-description: "This error occurs when MSBuild failed to write an internal file during a build."
-ms.date: "08/15/2022"
+title: MSB3101 diagnostic code
+description: Learn about the possible causes of the MSB3101 build error and get troubleshooting tips.
+ms.date: 04/14/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3101
@@ -18,12 +18,27 @@ ms.subservice: msbuild
 ---
 # MSB3101
 
+This article describes the MSB3101 error code.
+
+## Message text
+
+`Could not write state file 'filename'.`
+
+## Description
+
 This error occurs when MSBuild failed to write an internal file during a build. This error is not necessarily a blocking error, as MSBuild can sometimes recover from it and continue processing the build.
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
+
+Typical issues include:
+
+- The path is too long.
+- Permission is denied to the folder.
+- A file is locked by another process.
+- The disk is full.
 
-```output
-MSB3101: Could not write state file 'filename'
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem. Typical issues include: the path was too long, permission was denied to the folder, a file was locked by another process, or the disk was full.
+All versions of MSBuild
