Merge pull request #14067 from MicrosoftDocs/ghogen-patch-423906

MSB3277 is a warning, not an error

Author: ghogen

docs/msbuild/errors/msb3277.md

@@ -1,7 +1,7 @@
 ---
 title: MSB3277 diagnostic code
-description: Learn about the possible causes of the MSB3277 build error and get troubleshooting tips.
-ms.date: 05/16/2025
+description: Learn about the possible causes of the MSB3277 build warning and get troubleshooting tips.
+ms.date: 7/2/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3277
@@ -20,25 +20,25 @@ ms.subservice: msbuild
 
 <!-- :::ErrorDefinitionDescription::: -->
 <!-- :::editable-content name="introDescription"::: -->
-This article describes the MSB3277 error code.
+This article describes the MSB3277 warning.
 <!-- :::editable-content-end::: -->
 
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3277: Found conflicts between different versions of 'value' that could not be resolved.`
+`MSB3277: Found conflicts between different versions of 'assembly-name' that could not be resolved.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3277: Found conflicts between different versions of "{0}" that could not be resolved.
 {1} -->
 
 <!-- :::editable-content name="postOutputDescription"::: -->
 ## Description
 
-This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You can't reference two different and conflicting versions of the same assembly when building the same binary. The [ResolveAssemblyReference task](../resolveassemblyreference-task.md) emits this error. The task inspects all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on. The task works through the process until all assembly references are resolved.
+This warning occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You shouldn't reference two different and conflicting versions of the same assembly when building the same binary. The [ResolveAssemblyReference task](../resolveassemblyreference-task.md) emits this warning. The task inspects all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on. The task works through the process until all assembly references are resolved.
 
-## Diagnose the error
+## Diagnose the warning
 
-To diagnose the error, first enable diagnostic log output by using the `-verbosity:diag` command-line switch, and then check the MSBuild log file with the full diagnostics output. For longer 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.
+To diagnose the issue, first enable diagnostic log output by using the `-verbosity:diag` command-line switch, and then check the MSBuild log file with the full diagnostics output. For longer 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.
 
 In MSBuild 16.x or later, the specific assembly versions in conflict are written to the log file. In earlier versions of MSBuild, the content isn't added to the log file. Instead, follow the assembly dependency chain to locate the conflicting reference. Look at each assembly that your project references, and then the assemblies that the initial assemblies reference, and so on. Follow this process until you identify the conflicting assembly versions.
 
@@ -108,10 +108,10 @@ Visual Studio or settings in project files can enable or disable automatic bindi
 
 In advanced scenarios, your project might intentionally require more than one version of the same assembly. You can use special techniques to override the normal assembly loading process to accomplish the goal. For more information, see [Resolve assembly loads](/dotnet/standard/assembly/resolve-loads). Be sure to understand and follow the guidance in [Best practices for assembly loading](/dotnet/framework/deployment/best-practices-for-assembly-loading).
 
-For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md) and [How the runtime locates assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies).
+For a guide on resolving issues with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md) and [How the runtime locates assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies).
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
 ## Applies to
 
-All versions of MSBuild
+All versions of MSBuild