本文介绍了无法解决log4net之间的冲突的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在遇到问题之前会咳嗽,我已经做了很多尝试来找到解决方法,但是没有运气.在构建过程中,我不断收到错误消息

I am cough in front of a problem I have tried a lot to find the solution, but no luck. On build, I keep getting the error

" 1>  无法解决"log4net,版本= 1.2.10.0,区域性=中性,PublicKeyToken = 1b44e1d426115821"之间的冲突和"log4net,版本= 1.2.10.0,文化=中性,PublicKeyToken = 692fbea5521e1304". 选择"log4net,版本= 1.2.10.0,文化=中性,PublicKeyToken = 1b44e1d426115821".任意.

"1>  No way to resolve conflict between "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821" and "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304". Choosing "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821" arbitrarily.

1>  无法解决"log4net,版本= 1.2.13.0,文化=中性,PublicKeyToken = 669e0ddf0bb1aa2a"之间的冲突和"log4net,版本= 1.2.10.0,文化=中性,PublicKeyToken = 1b44e1d426115821". 选择"log4net,版本= 1.2.13.0,文化=中性,PublicKeyToken = 669e0ddf0bb1aa2a".任意."

1>  No way to resolve conflict between "log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a" and "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821". Choosing "log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a" arbitrarily."

按照建议寻找解决方案后,我尝试将重定向到web.config文件中的新版本,但不走运.

After looking for a solution, as suggested, I have tried to redirect to the new version in the web.config file no luck.

当尝试重新安装nuget软件包时,错误已添加具有相同密钥的项",并且同时,我找不到dll的任何引用,也找不到该密钥.

When trying to re-install the nuget package, error "An item with the same key has already been added", and at the same time, I could not find any references of the dll, nor the key. 

我已经清洗并重新构建了几次解决方案.我什至将dll添加到目录中,然后从web.config重定向到该目录.

I have cleaned and rebuild my solution several times. I even have added the dlls in a directory and redirected there from the web.config.

您能帮我这个忙吗?

newbie

推荐答案

如果您无法弄清引用的来源,则:a)查看Packages.config或b)打开详细信息生成输出,它将在生成输出中打印冲突的程序集.

If you are unable to figure out where the reference is coming from then: a) look in Packages.config or b) turn on detail build output and it'll print the conflicting assemblies in the build output.

迈克尔·泰勒
http://www.michaeltaylorp3.net

Michael Taylor
http://www.michaeltaylorp3.net


这篇关于无法解决log4net之间的冲突的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

07-30 06:24