Merged main into live

Author: mijacobs

docs/msbuild/errors/msb3275.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3275"
-description: "The primary reference 'name' could not be resolved because it has an indirect dependency on the assembly 'assembly-name' which was built against the 'version' framework. This is a higher version than the currently targeted framework 'version'."
-ms.date: "07/07/2021"
+title: MSB3275 diagnostic code
+description: Learn about the possible causes of the MSB3275 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3275
@@ -18,17 +18,22 @@ ms.subservice: msbuild
 ---
 # MSB3275
 
-The full error text is similar to the following output:
+This article describes the MSB3275 error code.
 
-```output
-The primary reference 'reference' could not be resolved because it has an indirect dependency on the assembly 'assembly-name' which was built against the 'version' framework. This is a higher version than the currently targeted framework 'version'.
-```
+## Message text
 
-Dependent assemblies can't be built against a higher version of the .NET Framework than you are currently building for. Consider targeting a newer version of the .NET Framework.
+`The primary reference 'reference' could not be resolved because it has an indirect dependency on the assembly 'assembly-name' which was built against the 'version' framework. This is a higher version than the currently targeted framework 'version'.`
 
-For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+## Description
 
-## See also
+Dependent assemblies can't be built against a higher version of the .NET Framework than the version you're currently building for. 
 
-- [MSBuild target framework and target platform](../msbuild-target-framework-and-target-platform.md)
-- [MSB3274](msb3274.md)
+## Resolution
+
+Consider targeting a newer version of the .NET Framework. For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+
+For more information, see [MSBuild target framework and target platform](../msbuild-target-framework-and-target-platform.md) and [MSB3274](msb3274.md).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3276.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3276"
-description: "This error occurs when MSBuild finds different conflicting versions of the same dependent assembly."
-ms.date: "08/15/2022"
+title: MSB3276 diagnostic code
+description: Learn about the possible causes of the MSB3276 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3276
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3276
 
+This article describes the MSB3276 error code.
+
+## Message text
+
+`MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.`
+
+## Description
+
 This error occurs when MSBuild finds different conflicting versions of the same dependent assembly.
 
-The full message resembles the following text:
+## Resolution
+
+The error output message suggests an appropriate way to resolve the error, if the version mismatch is intentional. The link in the output opens the article, [Enable and disable automatic binding redirection](/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection).
 
-```output
-MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.
-```
+## Applies to
 
-The message suggests an appropriate way to resolve the error, if the version mismatch is intentional. The link takes you to [How to: Enable and disable automatic binding redirection](/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection).
+All versions of MSBuild

docs/msbuild/errors/msb3277.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3277: Found conflicts between different versions of 'assembly' that could not be resolved"
-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."
-ms.date: "03/31/2021"
+title: MSB3277 diagnostic code
+description: Learn about the possible causes of the MSB3277 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3277
@@ -16,15 +16,27 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3277: Found conflicts between different versions of 'assembly' that could not be resolved
+# MSB3277
 
-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 cannot reference two different and conflicting versions of the same assembly when building the same binary. The error is emitted by the [ResolveAssemblyReference task](../resolveassemblyreference-task.md), which looks at all the referenced assemblies, and all of the assemblies referenced indirectly by those assemblies, and so on, until all assembly references have been resolved.
+This article describes the MSB3277 error code.
 
-## Diagnosing the error
+## Message text
 
-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. When this error occurs with MSBuild 16.x or later, the specific versions that are in conflict are written to the log file. If you're using an earlier version of MSBuild, this isn't in the log file, but you can usually follow the dependency chain to find the conflicting reference. Look at each of the assemblies your project references, and which assemblies those assemblies reference, and so on until you find the conflicting version(s).
+`MSB3277: Found conflicts between different versions of 'assembly' that could not be resolved.`
 
-The diagnostics log should specify not only which assembly versions were in conflict but exactly why they were considered, that is, there was a reference to *assembly1.dll*, which referenced *assembly2.dll* version x, but there was also a reference to *assembly2.dll* version y, and MSBuild could not figure out which was the right version to use.  The following is an excerpt from a diagnostic log showing a conflict between two versions of StreamJsonRpc:
+## 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.
+
+## Diagnose the error
+
+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.
+
+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.
+
+The diagnostics log should identify the specific assembly versions that are in conflict and the reasons for the conflicts. For example, a reference to *assembly1.dll*, which references *assembly2.dll* version **x**, but also references *assembly2.dll* version **y**. MSBuild can't determine which version to use for the assembly.
+
+The following example is an excerpt from a diagnostic log showing a conflict between two versions of `StreamJsonRpc`:
 
 ```output
 There was a conflict between "StreamJsonRpc, Version=2.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "StreamJsonRpc, Version=2.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
@@ -64,26 +76,32 @@ There was a conflict between "StreamJsonRpc, Version=2.1.0.0, Culture=neutral, P
     References which depend on "StreamJsonRpc, Version = 2.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [].
 ```
 
-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).
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. For more information, 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).
 
-## Common fixes
+## Resolution
 
-Depending on the root cause of the conflict, the fix might be to update the version of an assembly on disk, perhaps by upgrading or reinstalling a NuGet package or SDK. If you simply want to update all packages to the latest versions, you can run the command `Update-Package -reinstall` from the Package Manager Console in Visual Studio. See [Reinstalling and updating packages](/nuget/consume-packages/reinstalling-and-updating-packages). However, it could be that you intentionally have more than one version of the referenced assembly on disk, but your project or one of its dependencies needs to be updated so that it's referencing the latest version of the conflicting assembly that you have installed. The Global Assembly Cache (GAC) might also be a source of a potential conflict, in cases where you are referencing a specific version of an assembly, but the GAC overrides it. See [Global Assembly Cache](/dotnet/framework/app-domains/gac).
+How you resolve this issue depends on your project configuration and assembly dependency requirements:
 
-## Third-party components
+- Update the version of an assembly on disk by upgrading or reinstalling a NuGet package or SDK.
+- Update all packages to the latest versions with the `Update-Package -reinstall` command in the Package Manager Console for Visual Studio. For more information, see [Reinstalling and updating packages](/nuget/consume-packages/reinstalling-and-updating-packages).
+- For projects with multiple versions of a referenced assembly on disk, update the project or the dependencies to reference the latest version of the installed conflicting assembly. The Global Assembly Cache (GAC) might also be a source of a potential conflict, in cases where you reference a specific version of an assembly, but the GAC overrides it. For more information, see [Global Assembly Cache](/dotnet/framework/app-domains/gac).
 
-If the conflict is in a third-party component, the component might not be supported with the version of the conflicting assembly you're using in your project. Look to the third party to see if they offer an updated, compatible version. If that's not available, the solution might be to downgrade the version of the conflicting assembly you're referencing to match the version that the third party component uses.
+## External components
+
+If the conflict is in a non-Microsoft component, the component might not be supported with the version of the conflicting assembly you're using in your project. Check the provider of the other component to see if they offer an updated, compatible version. If a fix isn't available, the solution might be to downgrade the version of the conflicting assembly you're referencing to match the version that the other component uses.
 
 ## Binding redirects
 
-In some cases, your project might specify or might need to specify binding redirects, which force calls to use a specified version of an assembly. See [Redirecting assembly versions](/dotnet/framework/configure-apps/redirect-assembly-versions) to understand how binding redirects work. Visual Studio or settings in project files can enable or disable automatic binding redirection. See [How to: Enable and disable automatic binding redirection](/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection). Check the settings and make sure you understand how and why your project is using binding redirects.
+In some cases, your project might specify or might need to specify binding redirects, which force calls to use a specified version of an assembly. For more information, see [Redirecting assembly versions](/dotnet/framework/configure-apps/redirect-assembly-versions) to understand how binding redirects work.
+
+Visual Studio or settings in project files can enable or disable automatic binding redirection. For more information, see [Enable and disable automatic binding redirection](/dotnet/framework/configure-apps/how-to-enable-and-disable-automatic-binding-redirection). Check the settings and make sure you understand how and why your project is using binding redirects.
 
-## Loading multiple versions of the same assembly
+## Multiple versions of assembly loaded
 
-In advanced scenarios, it could also be that you're working with a project that intentionally requires more than one version of the same assembly. You can use special techniques to override the normal assembly loading process to accomplish the goal. 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).
+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).
+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).
 
-## See also
+## Applies to
 
-- [How the runtime locates assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies)
+All versions of MSBuild

docs/msbuild/errors/msb3284.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3284: Cannot get the file path for type library 'name' version 'version'."
-description: "This error occurs when MSBuild can't get the file path for a requested type library."
-ms.date: "08/15/2022"
+title: MSB3284 diagnostic code
+description: Learn about the possible causes of the MSB3284 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3284
@@ -18,14 +18,22 @@ ms.subservice: msbuild
 ---
 # MSB3284
 
+This article describes the MSB3284 error code.
+
+## Message text
+
+`MSB3284: Cannot get the file path for type library 'name' version 'version'.`
+
+## Description
+
 This error occurs when MSBuild can't get the file path for a requested type library.
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
+
+Look to the additional information provided by the operating system to determine the cause of the problem. Typical causes include incorrect or invalid GUIDs, incorrect version numbers, or a component isn't installed.
 
-```output
-MSB3284: Cannot get the file path for type library 'name' version 'version'.
-```
+Try checking the registry yourself to make sure the requested component is represented. For more information, see [COM registry keys](/windows/win32/com/com-registry-keys).
 
-Look to the additional information provided by the operating system to determine the cause of the problem. Typical causes include incorrect or invalid GUIDs, incorrect version numbers, or a component is not installed.
+## Applies to
 
-Try checking the registry yourself to make sure the requested component is represented. See [COM Registry Keys](/windows/win32/com/com-registry-keys).
+All versions of MSBuild

docs/msbuild/errors/msb3290.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3290: Failed to create the wrapper assembly for type library 'name'."
-description: "This error occurs when MSBuild tries to create the wrapper assembly for a type library, but the operating system returns an error."
-ms.date: "08/15/2022"
+title: MSB3290 diagnostic code
+description: Learn about the possible causes of the MSB3290 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3290
@@ -18,12 +18,21 @@ ms.subservice: msbuild
 ---
 # MSB3290
 
+This article describes the MSB3290 error code.
+
+## Message text
+
+`MSB3290: Failed to create the wrapper assembly for type library "{0}". {1}`
+
+
+## Description
+
 This error occurs when MSBuild tries to create the wrapper assembly for a type library, 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 to determine the cause of the problem.
 
-```output
-MSB3290: Failed to create the wrapper assembly for type library "{0}". {1}
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem.
+All versions of MSBuild