Update description metadata

Author: ghogen

docs/msbuild/errors/msb1060.md

@@ -1,6 +1,6 @@
 ---
 title: "MSB1060 diagnostic code"
-description: "Undefined environment variable passed in as switch."
+description: Learn about the possible causes of the MSB1060 MSBuild error, and get troubleshooting tips.
 ms.date: 4/17/2025
 ms.topic: "error-reference"
 f1_keywords:

docs/msbuild/errors/msb3178.md

@@ -1,7 +1,7 @@
 ---
 title: "MSB3178 diagnostic code"
 description: "Assembly 'value' is incorrectly specified as a file."
-ms.date: 12/06/2024
+ms.date: 4/17/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3178
@@ -21,19 +21,37 @@ ms.subservice: msbuild
 
 <!-- :::ErrorDefinitionDescription::: -->
 <!-- :::editable-content name="introDescription"::: -->
-This article describes the MSB3178 error code.
+This article describes the MSB3178 diagnostic code.
 <!-- :::editable-content-end::: -->
 
 ## Message text
 
-```output
-MSB3178: Assembly 'value' is incorrectly specified as a file.
-```
+`MSB3178: Assembly 'value' is incorrectly specified as a file.`
 
 <!-- :::editable-content name="postOutputDescription"::: -->
 <!--
 {StrBegin="MSB3178: "}
 -->
+## Description
+
+This warning occurs when MSBuild tries to process a manifest file, but encountered a file that looks like an assembly that was specified as an ordinary file, instead of using the correct XML structure for an assembly. Assembly manifests used in ClickOnce deployment for .NET applications are XML files that contain a XML-encoded of the contents of an application, which might include assemblies and files. Assemblies are specified using the `assembly` element, which also includes child elements such as as `assemblyInformation`; plain files are specified using the `file` element.
+
+In Visual Studio when you generate a ClickOnce manifest using the Publish process, you might get this warning if you specify a DLL or EXE with the `Build Action` set to `Content`. In Visual Studio, `Content` means add something as an ordinary file, not as an assembly. In a project file, `Content` is an item group. If the item group contains files that look like assemblies, you get this warning.
+
+## Resolution
+
+Check the assembly manifest XML file for the assembly given in the text of the error message. For more information, see [Assembly manifest](/dotnet/standard/assembly/manifest). You can generate a binary log to see why a particular file is being passed as an assembly. Use the `-bl` switch on the MSBuild command line, and then use the [MSBuild structured log viewer](https://msbuildlog.com) to open the binary log (`.binlog` file).
+
+If your project file contains an item group `Content` or your Visual Studio project specifies the `Build Action` as `Content` for some files with the DLL or EXE extension, consider whether this is intentional or not. 
+
+If your manifest file was generated by a custom tool or process, check any `file` elements to see if any of them reference files that should be referenced as assemblies instead (look for file extensions such as `.dll` or `.exe`.). If it was generated by a tool or MSBuild task, check the command line syntax, shell expansions, and validate any input files to the tool or task.
+
+You can disable this warning by using the `NoWarn` property:
+
+`<NoWarn>$(NoWarn);MSB3178</NoWarn>`
+
+You should only disable the warning if you've verified that including what appear to be assemblies as ordinary files is valid and intentional in your scenario.
+
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 

docs/msbuild/errors/msb3883.md

@@ -1,6 +1,6 @@
 ---
 title: "MSB3883 diagnostic code"
-description: "Unexpected exception:"
+description: Learn about the possible causes of the MSB3883 MSBuild error, and get troubleshooting tips.
 ms.date: 4/17/2025
 ms.topic: "error-reference"
 f1_keywords:

docs/msbuild/errors/msb3941.md

@@ -1,6 +1,6 @@
 ---
 title: "MSB3941 diagnostic code"
-description: "Failed to zip directory 'value' because it does not exist or is inaccessible."
+description: Learn about the possible causes of the MSB3941 MSBuild error, and get troubleshooting tips.
 ms.date: 4/17/2025
 ms.topic: "error-reference"
 f1_keywords: