Merge pull request #13824 from GitHubber17/415544-d

410544 - MSBuild error article updates

Author: v-regandowner

docs/msbuild/errors/msb3327.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3327"
-description: "Unable to find code signing certificate in the current user’s Windows certificate store."
-ms.date: "05/05/2022"
+title: MSB3327 diagnostic code
+description: Learn about the possible causes of the MSB3327 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
   - MSB3327
@@ -18,22 +18,30 @@ ms.subservice: msbuild
 ---
 # MSB3327
 
-The full error text is similar to the following example:
+This article describes the MSB3327 error code.
 
-```output
-MSB3327: Unable to find code signing certificate in the current user’s Windows certificate store. To correct this, either disable signing of the ClickOnce manifest or install the certificate into the certificate store.
-```
+## Message text
+
+`MSB3327: Unable to find code signing certificate in the current user’s Windows certificate store. To correct this, either disable signing of the ClickOnce manifest or install the certificate into the certificate store.`
+
+## Description
 
-You could get the error if you enabled **Sign the ClickOnce manifests** and the .pfx file specified for ClickOnce manifest signing could not be found in your certificate store when MSBuild was trying to publish the manifest.
+You might get this error if you enable the **Sign the ClickOnce manifests** feature, and the `.pfx` file specified for ClickOnce manifest signing isn't found in your certificate store when MSBuild tries to publish the manifest.
 
-To resolve this error, try re-importing the .pfx file again in the certificate store. To re-import the .pfx file, right-click the .pfx file in Windows Explorer and choose **Install PFX**.
+## Resolution
 
-![Screenshot of signing tab](media/msb3327/signing-install-pfx.png)
+To resolve this error, try reimporting the `.pfx` file in the certificate store. In Windows Explorer, right-click the `.pfx` file  and select **Install PFX**.
 
-See [How to: Sign application and deployment manifests](../../ide/how-to-sign-application-and-deployment-manifests.md) or for newer .NET projects in Visual Studio 2019 or later, see [Deploy a .NET Windows Desktop application using ClickOnce](../../deployment/quickstart-deploy-using-clickonce-folder.md).
+:::image type="content" source="media/msb3327/signing-install-pfx.png" alt-text="Screenshot of the Signing tab and the Sign the ClickOnce manifests option selected.":::
 
-When running in a non-interactive environment, such as a script in a pipeline, use the command-line tool [certutil](/windows-server/administration/windows-commands/certutil).
+For more information, see [Sign application and deployment manifests](../../ide/how-to-sign-application-and-deployment-manifests.md). For newer .NET projects in Visual Studio 2019 or later, see [Deploy a .NET Windows Desktop application by using ClickOnce](../../deployment/quickstart-deploy-using-clickonce-folder.md).
+
+When you run the program in a non-interactive environment, such as a script in a pipeline, use the command-line tool [certutil](/windows-server/administration/windows-commands/certutil):
 
 ```cmd
 certutil –f –p [certificate_password] –importpfx <path to pfx file>
 ```
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3482.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3482: An error occurred while signing"
-description: "This error occurs when MSBuild encounters an error while trying to sign an output file."
-ms.date: "08/15/2022"
+title: MSB3482 diagnostic code
+description: Learn about the possible causes of the MSB3482 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3482
@@ -18,26 +18,40 @@ ms.subservice: msbuild
 ---
 # MSB3482
 
-This error occurs when MSBuild encounters an error while trying to sign an output file when running the [SignFile task](../signfile-task.md).
+This article describes the MSB3482 error code.
 
-The message resembles the following, but this text is followed by additional information from the signing tool:
+## Message text
 
-```output
-MSB3482: An error occurred while signing:
-```
+`MSB3482: An error occurred while signing:`
+
+## Description
+
+This error occurs when MSBuild encounters an error when it tries to sign an output file while running the [SignFile task](../signfile-task.md). 
+
+## Resolution
 
-Check that the sign file exists.  
+First, confirm the sign file exists. Next, make sure the signing tool is installed (the tool is installed as part of Visual Studio).
 
-Make sure the signing tool is installed; it's installed with Visual Studio. Look to the additional information provided by the signing tool to see more about what happened.
+The standard output message text is followed by additional information from the signing tool. Look to the additional information to determine the cause of the problem. If the error mentions an option that isn't supported, such as the `/fd` option, you might have an older version of the *signtool.exe* file on your system. When the process encounters the older or unsupported version of the file, MSBuild returns this error message.
 
-If the error mentions an option that isn't supported, like the `/fd` option, you might have an older version of *signtool.exe* that was found on the system. MSBuild needs the version installed with Visual Studio or the .NET SDK. The fix depends on your specific situation, but possible fixes include editing the PATH environment variable to reorder the directories, uninstalling, renaming, or otherwise hiding the old *signtool.exe*, or uninstalling or updating the software package it's a part of, for example, updating an old version of the Windows SDK.
+MSBuild works with the version of the tool in the Visual Studio or .NET SDK installation. The fix for the issue depends on your specific situation. Here are some possible solutions:
 
-If the thumbprint is invalid, it will trigger a cryptographic error, and you might see this error. Check the string value given as the `CertificateThumbprint` parameter to the `SignFile` task. The certificate thumbprint is the SHA-1 hash of the certificate. For more information, see [Obtain the SHA-1 hash of a trusted root CA certificate](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733076\(v\=ws.10\)). If you copy and paste the thumbprint from the certificate details, make sure you do not include the extra (3F) invisible character, which may prevent `SignFile` from finding the certificate.
+- Edit the PATH environment variable and reorder the directories
+- Uninstall, rename, or otherwise hide the older version of the *signtool.exe* tool
+- Uninstall or update the software package that contains the tool, such as updating an older version of the Windows SDK
 
-Test certificates expire after a period of time. You might have to create a new one. See [How to: Sign application and deployment manifests](../../ide/how-to-sign-application-and-deployment-manifests.md) or for newer .NET projects in Visual Studio 2019 or later, see [Deploy a .NET Windows Desktop application using ClickOnce](../../deployment/quickstart-deploy-using-clickonce-folder.md).
+### Invalid thumbprint or certificate
 
-When running in a non-interactive environment, such as a script in a pipeline, you can create a certificate by using the command-line tool [certutil](/windows-server/administration/windows-commands/certutil).
+If the thumbprint is invalid, it triggers a cryptographic error, and you might see the MSB3482 error. Check the string value for the `CertificateThumbprint` parameter to the `SignFile` task. The certificate thumbprint is the SHA-1 hash of the certificate. For more information, see [Obtain the SHA-1 hash of a trusted root CA certificate](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc733076\(v\=ws.10\)). If you copy and paste the thumbprint from the certificate details, make sure you don't include the extra (`3F`) invisible character, which can prevent the `SignFile` task from finding the certificate.
+
+Test certificates expire after a period of time. You might have to create a new certificate. For more information, see [Sign application and deployment manifests](../../ide/how-to-sign-application-and-deployment-manifests.md). For newer .NET projects in Visual Studio 2019 or later, see [Deploy a .NET Windows Desktop application using ClickOnce](../../deployment/quickstart-deploy-using-clickonce-folder.md).
+
+When you run the program in a non-interactive environment, such as a script in a pipeline, you can create a certificate by using the command-line tool [certutil](/windows-server/administration/windows-commands/certutil):
 
 ```cmd
 certutil –f –p [certificate_password] –importpfx <path to pfx file>
 ```
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3491.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3491: Could not write lines to file 'filename'."
-description: "This error occurs when MSBuild tries to write to a file, but the operating system returns an error."
-ms.date: "08/15/2022"
+title: MSB3491 diagnostic code
+description: Learn about the possible causes of the MSB3491 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3491
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3491
 
+This article describes the MSB3491 error code.
+
+## Message text
+
+`MSB3491: Could not write lines to file 'filename'.`
+
+## Description
+
 This error occurs when MSBuild tries to write to a file, but the operating system returns an error.
 
-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 by the operating system to determine the cause of the problem.
 
-```output
-MSB3491: Could not write lines to file 'filename'.
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem.
+All versions of MSBuild

docs/msbuild/errors/msb3541.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3541: 'entity' has invalid value 'value'."
-description: "This error occurs when an invalid value for an MSBuild element or attribute was found during the processing of a project file."
-ms.date: "08/15/2022"
+title: MSB3541 diagnostic code
+description: Learn about the possible causes of the MSB3541 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3541
@@ -18,14 +18,22 @@ ms.subservice: msbuild
 ---
 # MSB3541
 
-This error occurs when an invalid value for the `Path` or `Files` arguments were found during the execution of the  `FindUnderPath` task. See [FindUnderPath task](../findunderpath-task.md).
+This article describes the MSB3541 error code.
 
-The message resembles the following, but this text is followed by the exception text from the underlying code:
+## Message text
 
-```output
-MSB3541: 'entity' has invalid value 'value'.
-```
+`MSB3541: 'entity' has invalid value 'value'.`
+
+## Description
+
+This error occurs when an invalid value for the `Path` or `Files` arguments is found during execution of the  `FindUnderPath` task. For more information, see [FindUnderPath task](../findunderpath-task.md). The error output message is followed by the exception text from the underlying code.
+
+## Resolution
 
 Look to the exception message provided by the underlying code to determine the cause of the problem.
 
 Check the syntax of the element and its attributes that resulted in the error.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3552.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3552: Resource file 'filename' cannot be found"
-description: "This error occurs when a request resource file was not found. Check the path and spelling of the filename."
-ms.date: "06/18/2021"
+title: MSB3552 diagnostic code
+description: Learn about the possible causes of the MSB3552 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3552
@@ -16,6 +16,22 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3552: Resource file 'filename' cannot be found
+# MSB3552
 
-This error occurs when a request resource file was not found. Check the path and spelling of the filename. These files are generally specified as `EmbeddedResource` items in the project file.
+This article describes the MSB3552 error code.
+
+## Message text
+
+`MSB3552: Resource file 'filename' cannot be found.`
+
+## Description
+
+This error occurs when a requested resource file isn't found.
+
+## Resolution
+
+Check the path and spelling of the filename. These files are often specified as `EmbeddedResource` items in the project file.
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3553.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3553: Resource file 'name' has an invalid name"
-description: "This error occurs when there's a problem with the name of a resource file."
-ms.date: "07/07/2021"
+title: MSB3553 diagnostic code
+description: Learn about the possible causes of the MSB3553 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3553
@@ -16,8 +16,24 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# Resource file 'name' has an invalid name
+# MSB3553
 
-This error occurs when there's a problem with the name of a resource file. Check that the file has an extension appropriate to its type (for example, .resx), and that it doesn't contain any characters that are not allowed by the operating system. Refer to your operating system documentation for characters that are invalid in a filename or path. For Windows, see [Naming a file](/windows/win32/fileio/naming-a-file#naming-conventions).
+This article describes the MSB3553 error code.
 
-This error could also occur if paths exceed the maximum path length. If you use long paths, check the Windows operating system LongPathsEnabled setting. See [Maximum file path limitation](/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd).
+## Message text
+
+`MSB3553: Resource file 'name' has an invalid name.`
+
+## Description
+
+This error occurs when there's a problem with the name of a resource file.
+
+## Resolution
+
+Verify that the file extension corresponds to the file type (for example, `.resx`). Confirm the file doesn't contain any invalid characters as define by the operating system. Refer to your operating system documentation for characters that are invalid in a filename or path. For Windows, see [Naming a file](/windows/win32/fileio/naming-a-file#naming-conventions).
+
+This error can also occur when file paths exceed the maximum path length. If you use long paths, check the Windows operating system `LongPathsEnabled` setting. For more information, see [Maximum file path limitation](/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3554.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3554: Cannot write to the output file 'filename'."
-description: "This error occurs when MSBuild encounters a problem when trying to write to a specific output file."
-ms.date: "06/18/2021"
+title: MSB3554 diagnostic code
+description: Learn about the possible causes of the MSB3554 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3554
@@ -16,9 +16,24 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3554: Cannot write to the output file 'filename'
+# MSB3554
 
-This error occurs when MSBuild encounters a problem when trying to write to a specific output file. When you see this error, the error text from the operating system is also shown just after it. Look to the specific error text for additional information about the problem.
+This article describes the MSB3554 error code.
 
-A common cause is that the output file is in use by another process. Close other applications that might be using the same file, and try building again.
+## Message text
 
+`MSB3554: Cannot write to the output file 'filename'.`
+
+## Description
+
+This error occurs when MSBuild encounters a problem when trying to write to a specific output file. A common cause is that the output file is in use by another process. The error message output is followed by the specific error text 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 by the operating system to determine the cause of the problem.
+
+Close other applications that might be using the same file, and try building again.
+
+## Applies to
+
+All versions of MSBuild