Programming Tutorials

Severity Code Description Project File Line Suppression State Warning Found conflicts between different versions of the same dependent assembly.

By: Niraj in Asp.net Tutorials on 2023-06-01  

Severity Code Description Project File Line Suppression State Warning Found conflicts between different versions of the same dependent assembly.

If you look futher in the error message, you will have something like "In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.ValueTuple" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" /><bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" /></dependentAssembly></assemblyBinding>".

The warning you're seeing indicates that there are conflicts between different versions of the same dependent assembly in your project. To resolve this warning, you can add binding redirects to your application configuration file.

To fix the conflicts, follow these steps:

1. Open the application configuration file (web.config for web applications or app.config for non-web applications) in your project.

2. Locate the <runtime> element within the <configuration> element.

3. If there's no existing <assemblyBinding> element within the <runtime> element, add the following code snippet:

   <runtime>
     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
       <dependentAssembly>
         <assemblyIdentity name="System.ValueTuple" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
         <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
       </dependentAssembly>
     </assemblyBinding>
   </runtime>

4. Save the configuration file.

By adding the binding redirects, you're specifying that any version of the System.ValueTuple assembly within the range of 0.0.0.0 to 4.0.3.0 should be redirected to version 4.0.3.0.

After making these changes, rebuild your project, and the warning should be resolved.