0

I am getting the below in the output window when building the dotnet project.

No way to resolve conflict between "Microsoft Practices EnterpriseLibrary Common, Version=5.0.414.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxx" and "Microsoft Practices EnterpriseLibrary Common, Version=4.1.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxx. Choosing "Microsoft Practices EnterpriseLibrary Common, Version=5.0.414.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxx" arbitrarily.

Microsoft.Practices.EnterpriseLibrary.Common only two projects in my solution contain this dll file referenced in them and only for Version=5.0.414.0.I am not sure why the above conflict is coming in the output window. Can anyone suggest how to resolve this conflict.

I am using Visual Studio 2017.

Target Framework for all the projects is NetFramework 4.

My Point Of View
  • 1
  • Please provide a [mcve] - at the moment we have no idea what other dependencies you might have. (I'd also strongly advise updating both VS and your target framework - the lowest supported version of .NET Framework that's currently supported by MS is 4.6.2.) – Jon Skeet Sep 20 '22 at 08:11
  • Probably some other packages you referenced might be internally depending on the same library but different version. You can add a [binding redirect](https://stackoverflow.com/questions/43365736/assembly-binding-redirect-how-and-why) and see if that resolves the issue. – Mat J Sep 20 '22 at 08:17
  • Does this answer your question? [Assembly Binding redirect: How and Why?](https://stackoverflow.com/questions/43365736/assembly-binding-redirect-how-and-why) – Mat J Sep 20 '22 at 08:17
  • @MatJ the Public token key is different so I don't think Assembly Binding redirect will work. – My Point Of View Sep 20 '22 at 10:08
  • Have you tried remaking a new project and then copying the code over to it? it's Probabbly a messed up project. – Nullify Sep 20 '22 at 10:19

0 Answers0