Consider app.config remapping of assembly with no app.config mapping

user_280602 0
Viewed 45416

How can I determine where to fix this reference without adding a binding to the app.config?

Consider app.config remapping of assembly "System.Runtime.Serialization.Primitives, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "4.1.1.0" [] to Version "4.1.2.0" [F:\Production\packages\System.Runtime.Serialization.Primitives.4.3.0\lib\net46\System.Runtime.Serialization.Primitives.dll] to solve conflict and get rid of warning. 12>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3247: Found conflicts between different versions of the same dependent assembly. 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:

nuget visual-studio assemblies .net
4 Answers

I solved this by targeting a higher .Net Framework version. Switched from 4.7 to 4.7.2 and the warnings went away. The warnings started after I switched from EF6 to EF.Core

user_23935590

The real problem is that the References in the .csproj file are not updated when doing a nuget update, hence the warning to override these in the app.config. If you update the .csproj, all warnings go away.

user_651890

I began getting the error when I upgraded the Microsoft Identity packages (via NuGet). Some of the version numbers were not updated in the <runtime> node of the web.config file. I found this fix by following Leo Liu-MSFT's instructions (above).

user_42707090
Related