Clever Geek Handbook

Consider reassigning assembly app.config without mapping app.config

How can I determine where to fix this link without adding a binding to 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:

+18


source to share


2 answers


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

You can try changing the "verbosity of the MSBuild project output" to " Verbose " or higher to check the verbosity error log for details. To do this, use Tools -> Options ...-> Projects and Solutions-> Build and Run . Set the level of detail of the output of the project MSBuild details or higher. Build a project and check the error log in the output window. The ResolveAssemblyReferences task, which is the task that MSB3247 starts with, should help you debug this particular issue.



enter image description here

Then go to the project with the old version, remove the link, then add the correct link.

+30


source


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



0


source






More articles:


All Articles