blocks|key|3375276|text|基本上，当您引用的程序集的"Copy+Local“设置为"True”时，就会发生这种情况，这意味着DLL的副本与您的exe一起放在bin文件夹中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375277|由于Visual+Studio还将复制被引用程序集的所有依赖项，因此最终可能会引用同一程序集的两个不同版本。如果您的项目位于不同的解决方案中，则更有可能发生这种情况，因此可以单独编译。|3375278|我解决这个问题的方法是将程序集项目中的引用的Copy+Local设置为False。只对可执行文件/web应用程序执行此操作，在这些应用程序中，您需要运行最终产品的程序集。|3375279|希望这是有意义的！|3375280|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Basically this happens when the assemblies you're referencing have "Copy Local" set to "True", meaning that a copy of the DLL is placed in the bin folder along with your exe.

Since Visual Studio will copy all of the dependencies of a referenced assembly as well, it's possible to end up with two different builds of the same assembly being referred to. This is more likely to happen if your projects are in separate solutions, and can therefore be compiled separately.

The way I've gotten around it is to set Copy Local to False for references in assembly projects. Only do it for executables/web applications where you need the assembly for the finished product to run.

Hope that makes sense!

blocks|key|3375389|text|这实际上取决于您的外部组件。当您在.NET应用程序中引用外部组件时，它会生成一个GUID来标识该组件。当其中一个项目引用的外部组件与另一个程序集中的另一个此类组件具有相同的名称但版本不同时，就会发生此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375390|当您使用"Browse“查找引用并添加错误版本的程序集时，或者代码存储库中的组件版本与本地计算机中安装的组件版本不同时，有时会发生这种情况。|3375391|一定要尝试找出哪些项目有这些冲突，从引用列表中删除组件，然后再次添加它们，确保您指向相同的文件。|3375392|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This actually depends on your external component. When you reference an external component in a .NET application it generates a GUID to identify that component. This error occurs when the external component referenced by one of your projects has the same name and but different version as another such component in another assembly.

This sometimes happens when you use "Browse" to find references and add the wrong version of the assembly, or you have a different version of the component in your code repository as the one you installed in the local machine.

Do try to find which projects have these conflicts, remove the components from the reference list, then add them again making sure that you're pointing to the same file.

blocks|key|3162612|text|此警告意味着两个项目引用了相同的程序集(例如System.Windows.Forms)，但这两个项目需要不同的版本。您有几个选项：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3162613|3162614|重新编译所有项目以使用相同的版本(例如，全部迁移到.Net+3.5)。这是首选选项，因为所有代码都使用编译时使用的依赖项版本运行。|ordered-list-item|3162615|添加binding+redirect。这将禁止显示警告。但是，您的.Net+2.0项目将(在运行时)绑定到.Net+3.5版本的依赖程序集，如System.Windows.Forms。你可以在Visual+Studio中双击error来快速添加绑定重定向。|3162616|使用CopyLocal=true。我不确定这是否会抑制警告。与上面的选项2一样，这意味着所有项目都将使用System.Windows.Forms.|3162617|的.Net+3.5版本|3162618|以下是识别违规引用的几种方法：|3162619|3162620|您可以使用https://gist.github.com/1553265+|unordered-list-item|3162621|中提供的实用程序。另一种简单的方法是设置生成输出详细信息(“工具”、“选项”、“项目和解决方案”、“生成并运行”、“MSBuild项目生成输出详细信息”)，并在生成之后，在“输出”窗口中搜索警告，然后查看警告上方的文本。(向在对这个答案的评论中提出这个建议的致敬)。|3162622|3162623|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/433ysdt1.aspx|1|https://gist.github.com/1553265^0|M|K|0|0|0|1Z|K|2|G|0|0|2|E|0|0|0|0|5|V|1|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|I|7|1D|8|@$9|1E|A|1F|B|C]]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|L|3|M|5|I|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1M|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1N|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]|$1|S|3|T|5|U|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|V|3|W|5|U|7|1T|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]|16|$5|11|12|13|E|$14|17]]]]

This warning means that two projects reference the same assembly (e.g. <code>System.Windows.Forms</code>) but the two projects require different versions. You have a few options:

<ol>
<li>Recompile all projects to use the same versions (e.g. move all to .Net 3.5). This is the preferred option because all code is running with the versions of dependencies they were compiled with.</li>
<li>Add a <a href="http://msdn.microsoft.com/en-us/library/433ysdt1.aspx" rel="noreferrer">binding redirect</a>. This will suppress the warning. However, your .Net 2.0 projects will (at runtime) be bound to the .Net 3.5 versions of dependent assemblies such as <code>System.Windows.Forms</code>. You can quickly add a binding redirect by double-clicking on error in Visual Studio.</li>
<li>Use <code>CopyLocal=true</code>. I'm not sure if this will suppress the warning. It will, like option 2 above, mean that all projects will use the .Net 3.5 version of System.Windows.Forms.</li>
</ol>

Here are a couple of ways to identify the offending reference(s):

<ul>
<li>You can use a utility such as the one found at
<a href="https://gist.github.com/1553265" rel="noreferrer">https://gist.github.com/1553265</a> </li>
<li>Another simple method is to set Build
output verbosity (Tools, Options, Projects and Solutions, Build and
Run, MSBuild project build output verbosity, Detailed) and after
building, search the output window for the warning, and look at the
text just above it. (Hat tip to <a href="https://stackoverflow.com/users/44547/pauloya">pauloya</a> who suggested this in the
comments on this answer).</li>
</ul>

blocks|key|3162645|text|我刚刚收到了这条警告消息，清理了解决方案并重新编译(Build+->+Clean+Solution)，它就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162646|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just had this warning message and cleaned the solution and recompiled (Build -> Clean Solution) and it went away.

blocks|key|3162693|text|我在我的一个项目中遇到了同样的问题，然而，上面的这些都没有帮助解决这个警告。我检查了详细的构建日志文件，我使用AsmSpy验证了我在受影响的解决方案中为每个项目使用了正确的版本，我仔细检查了每个项目文件中的实际条目-没有任何帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162694|最终发现问题是我在一个项目中的一个引用的嵌套依赖。这个引用(A)反过来需要一个不同版本的(B)，它直接从我的解决方案中的所有其他项目中引用。在被引用的项目中更新引用解决了这个问题。|3162695|Solution+A
%2B--Project+A
+++%2B--Reference+A+(version+1.1.0.0)
+++%2B--Reference+B
%2B--Project+B
+++%2B--Reference+A+(version+1.1.0.0)
+++%2B--Reference+B
+++%2B--Reference+C
%2B--Project+C
+++%2B--Reference+X+(this+indirectly+references+Reference+A,+but+with+e.g.+version+1.1.1.0)

Solution+B
%2B--Project+A
+++%2B--Reference+A+(version+1.1.1.0)|code-block|syntax|javascript|3162696|我希望上面的说明说明了我的意思，我花了几个小时才找到答案，所以希望其他人也能从中受益。|3162697|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had the same problem with one of my projects, however, none of the above helped to solve the warning. I checked the detailed build logfile, I used AsmSpy to verify that I used the correct versions for each project in the affected solution, I double checked the actual entries in each project file - nothing helped.

Eventually it turned out that the problem was a nested dependency of one of the references I had in one project. This reference (A) in turn required a different version of (B) which was referenced directly from all other projects in my solution. Updating the reference in the referenced project solved it.

<pre><code>Solution A
+--Project A
 +--Reference A (version 1.1.0.0)
 +--Reference B
+--Project B
 +--Reference A (version 1.1.0.0)
 +--Reference B
 +--Reference C
+--Project C
 +--Reference X (this indirectly references Reference A, but with e.g. version 1.1.1.0)

Solution B
+--Project A
 +--Reference A (version 1.1.1.0)
</code></pre>

I hope the above shows what I mean, took my a couple of hours to find out, so hopefully someone else will benefit as well.

blocks|key|3162721|text|这也发生在我身上。一个dll被引用了两次:一次是直接引用(在引用中)，另一次是间接引用(由另一个引用的项目引用)。我删除了直接引用，清理和重建了解决方案。问题已修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162722|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This happened to me too. One dll was referenced twice: once directly (in references) and once indirectly (referenced by another referenced project). 
I removed direct reference, cleaned &amp; rebuilt solution. Problem fixed.

blocks|key|3162802|text|如果你使用Nuget来管理你的依赖关系，我还有另外一种方法。我发现有时候VS和Nuget不匹配，Nuget无法识别您的项目不同步。packages.config将说明一件事，但在引用-属性中显示的路径将说明另一件事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162803|如果您愿意更新您的依赖项，请执行以下操作：|3162804|在解决方案资源管理器中，右键单击项目并单击左侧窗格中的'Manage+Nuget+Packages'|3162805|Select+'Installed+packages‘标签记录您的已安装软件包如果您有很多的话，可能要先将您的packages.config复制到您的桌面，这样您就可以与谷歌交叉检查它，以了解哪些Nuget+pkgs是您的软件包。好的，我们将添加它们，back.|unordered-list-item|3162806|
|3162807|Immediately安装你需要的包。Nuget所做的不仅是为您获取最新版本，还将更改您的引用，并为您添加绑定重定向。|3162808|3162809|为您的所有项目执行此操作。|3162810|3162811|在解决方案级别，执行清理并重建。|3162812|3162813|您可能希望从较低的项目开始，然后一直工作到较高级别的项目，并在进行过程中重新构建每个项目。|3162814|如果您不想更新依赖项，那么可以使用包管理器控制台，并使用语法Update-Package+-ProjectName+yourProjectName+-Version+versionNumber|3162815|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|14|8|@]|9|@]|A|$]]|$1|M|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|H|7|16|8|@]|9|@]|A|$]]|$1|P|3|J|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|18|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1A|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1B|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Y|$]]

I have another way to do this if you're using Nuget to manage your dependencies. I've discovered that sometimes VS and Nuget don't match up and Nuget is unable to recognize that your projects are out of sync. The packages.config will say one thing but the path shown in References - Properties will indicate something else. 

If you're willing to update your dependencies, do the following:

<ol>
<li>From Solution Explorer, right click the Project and click 'Manage
Nuget Packages'</li>
<li>Select 'Installed packages' tab in left pane Record your installed
 packages You may want to copy your packages.config to your
 desktop first if you have a lot, so you can cross check it with
 Google to see what Nuget pkgs are installed</li>
<li>Uninstall your packages. Its OK, we're going to add them right back.</li>
<li>Immediately install the packages you need. What Nuget will do is not only get you the latest version, but will alter your references, and also add the binding redirects for you.</li>
<li>Do this for all of your projects.</li>
<li>At the solution level, do a Clean and Rebuild.</li>
</ol>

You may want to start with the lower projects and work your way to the higher level ones, and rebuild each project as you go along.

If you don't want to update your dependencies, then you can use the package manager console, and use the syntax Update-Package -ProjectName [yourProjectName] [packageName] -Version [versionNumber]

blocks|key|3375680|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375681|打开"Solution+Explorer".|ordered-list-item|3375682|Click+on“显示所有文件”|3375683|展开查看一个(或多个)引用，其图标与其他引用略有不同。通常，它会带有黄色方框，建议您记下笔记。只需删除它。|3375684|将引用添加回来并编译您的代码。|3375685|仅此而已。|3375686|3375687|在我的例子中，MySQL引用出现了问题。不知何故，我可以在所有可用的参考资料列表中列出它的三个版本；对于.net+2.0，.net+4.0和.net+4.5。我遵循上面的过程1到6，它对我起作用了。|3375688|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|R|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|S|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|T|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|U|7|@]|8|@]|9|$]]|$1|J|3|K|4|C|6|V|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|X|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]]|P|$]]

<ol>
<li>Open "Solution Explorer".</li>
<li>Click on "Show all files"</li>
<li>Expand "References"</li>
<li>You'll see one (or more) reference(s) with slightly different icon than the rest. Typically, it is with yellow box suggesting you to take a note of it. Just remove it.</li>
<li>Add the reference back and compile your code.</li>
<li>That's all.</li>
</ol>

In my case, there was a problem with MySQL reference. Somehow, I could list three versions of it under the list of all available references; for .net 2.0, .net 4.0 and .net 4.5. I followed process 1 through 6 above and it worked for me.

blocks|key|3375699|text|我也遇到了同样的问题，我在web.config中修改了下面的代码来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375700|这发生在我身上，因为我正在使用Newtonsoft.Json+4.0运行应用程序|3375701|发自：|3375702|<dependentAssembly>
++<assemblyIdentity+name="Newtonsoft.Json"+publicKeyToken="30ad4fe6b2a6aeed"+culture="neutral"+/>
++<bindingRedirect+oldVersion="0.0.0.0-6.0.0.0"+newVersion="6.0.0.0"+/>
</dependentAssembly>|code-block|syntax|javascript|3375703|至：|3375704|<dependentAssembly>
++<assemblyIdentity+name="Newtonsoft.Json"+publicKeyToken="30ad4fe6b2a6aeed"+culture="neutral"+/>
++<bindingRedirect+oldVersion="0.0.0.0-6.0.0.0"+newVersion="4.5.0.0"+/>
</dependentAssembly>|3375705|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I had the same issue and I resolved by changing the following in web.config.

It happened to me because I am running the application using Newtonsoft.Json 4.0 

From:

<pre><code>&lt;dependentAssembly&gt;
 &lt;assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /&gt;
 &lt;bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" /&gt;
&lt;/dependentAssembly&gt;
</code></pre>

To:

<pre><code>&lt;dependentAssembly&gt;
 &lt;assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /&gt;
 &lt;bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="4.5.0.0" /&gt;
&lt;/dependentAssembly&gt;
</code></pre>

blocks|key|367329|text|同样也有这个问题--在我的例子中，它是由许多引用的"Specific+Version“属性设置为true引起的。在这些引用上将其更改为false解决了该问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367330|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Also had this problem - in my case it was caused by having the "Specific Version" property on a number of references set to true. Changing this to false on those references resolved the issue.

blocks|key|3162920|text|我想发布他们在上面的评论中提供的pauloya的解决方案。我相信这是找到令人不快的引用的最佳解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162921|要查找什么是“令人不快的引用”，最简单的方法是设置生成输出详细信息(工具、选项、项目和解决方案、生成和运行、MSBuild项目生成输出详细信息)，并在生成之后，在输出窗口中搜索警告。查看其正上方的文本。|3162922|3162923|例如，当您在output面板中搜索"conflict“时，您可能会找到类似以下内容：|3162924|3>++There+was+a+conflict+between+"EntityFramework,+Version=5.0.0.0,+Culture=neutral,+PublicKeyToken=b77a5c561934e089"+and+"EntityFramework,+Version=6.0.0.0,+Culture=neutral,+PublicKeyToken=b77a5c561934e089".
3>++++++"EntityFramework,+Version=5.0.0.0,+Culture=neutral,+PublicKeyToken=b77a5c561934e089"+was+chosen+because+it+was+primary+and+"EntityFramework,+Version=6.0.0.0,+Culture=neutral,+PublicKeyToken=b77a5c561934e089"+was+not.|code-block|syntax|javascript|3162925|如您所见，EF版本5和6之间存在冲突。|3162926|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|T|8|@]|9|@]|A|$J|K]]|$1|L|3|M|5|6|7|U|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|O|$]]

I wanted to post pauloya's solution they provided in the comments above. I believe it is the best solution for finding the offending references.

<blockquote>
 The simplest way to find what are the "offending reference(s)" is to
 set Build output verbosity (Tools, Options, Projects and Solutions,
 Build and Run, MSBuild project build output verbosity, Detailed) and
 after building, search the output window for the warning. See the text
 just above it.
</blockquote>

For example, when you search the output panel for "conflict" you may find something like this:

<pre><code>3&gt; There was a conflict between "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
3&gt; "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was chosen because it was primary and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was not.
</code></pre>

As you can see, there is a conflict between EF versions 5 and 6.

blocks|key|3375812|text|在Visual+Studio中，如果你右击solution和Manage+nuget+packages，就会出现一个"Consolidate"标签，它会将所有的软件包设置为相同的版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3375813|entityMap^0|L|8|U|L|1M|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

On Visual Studio if you right click on the solution and Manage nuget packages theres a "Consolidate" tab which sets all the packages to the same version.

blocks|key|366980|text|=>检查是否会部分安装应用程序的某些实例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366981|=>首先从卸载应用程序中卸载该实例。|366982|然后使用=>，清理、重新构建并尝试部署。|366983|这解决了我的issue.hope，对你也有帮助。诚挚的问候。|366984|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

=> check there will be some instance of application installed partially. 

=> first of all uninstall that instance from uninstall application.

=> then,clean,Rebuild,and try to deploy.

this solved my issue.hope it helps you too.
Best Regards.

blocks|key|3163034|text|另一件需要考虑和检查的事情是，确保您没有任何使用bin文件夹的服务正在运行。如果是停止服务并重建解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3163035|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another thing to consider and check is, make sure you don't have any service running that's using that bin folder. if their is stop the service and rebuild solution

blocks|key|3375860|text|在编辑.resx文件时，Mac+Visual+Studio上似乎有一个问题。我真的不知道发生了什么，但当我在我的苹果电脑上编辑一些.resx文件时，我就遇到了这个问题。我在Windows上打开了这个项目，打开了文件，它们就像没有被编辑过一样。所以我编辑了它们，保存了它们，然后一切都开始在Mac上运行了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375861|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There seems to be a problem on Mac Visual Studio when editing .resx files. 
I don't really know what happened, but I got this problem as soon as I edited some .resx files on my Mac.
I opened the project on Windows, opened the files and they were as if they haven't been edited.
So I edited them, saved, and everything started working again on Mac too.

blocks|key|3375876|text|当我的项目引用了NETStandardLibrary，并且为netcore发布了一个引用的程序集时，我遇到了这样的问题。我刚把它作为netstandard发布，问题就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375877|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had such issue when my project had reference to NETStandardLibrary and one of referenced assemblies was published for netcore. Just published it as netstandard and problem was gone

blocks|key|3163088|text|如果使用NuGet，我所要做的就是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3163089|3163090|右键单击项目，然后单击管理NuGet+Packages。|ordered-list-item|3163091|在binding+Redirects|3163092|Clean+|3163093|+rebuild中单击右上角的齿轮，然后在NuGet包管理器中单击常规选项卡，包源和选中"Skip+Applying+redirects“|3163094|rebuild|3163095|NuGet‘s+gone|3163096|3163097|简单易用|3163098|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|11|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

If using NuGet all I had to do was:

<ol>
<li>right click project and click Manage NuGet Packages.. </li>
<li>click the cog in top right</li>
<li>click General tab in NuGet Package Manager above Package Sources</li>
<li>check "Skip Applying binding redirects" in Binding Redirects</li>
<li>Clean and rebuild and the warning's gone</li>
</ol>

Easy peasy

blocks|key|3163111|text|我只是花了一些时间来调试同样的问题。注意，这个问题可能不是在不同的项目之间，而是实际上是在一个项目中的几个引用之间，这些引用依赖于同一dll/程序集的不同版本。在我的例子中，问题是引用FastMember.dll版本不匹配，它来自单个项目中的两个不同的NuGet包。当我得到一个项目时，它不会编译，因为NuGet包丢失了，并且VS拒绝恢复丢失的包。通过NuGet菜单，我手动将所有NuGets更新到最新版本，也就是出现警告的时候。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3163112|在Visual+Studio+Tools+>+Options+>+Build+and+Run+>+MSBuld+Project+build+output+verbosity:+(set+to)+Diagnostics.中，在Output窗口中查找行There+was+a+conflict+between。下面是我得到的输出部分：|3163113|1>++There+was+a+conflict+between+"FastMember,+Version=1.5.0.0,+Culture=neutral,+PublicKeyToken=null"+and+"FastMember,+Version=1.3.0.0,+Culture=neutral,+PublicKeyToken=null".+(TaskId:19)
1>++++++"FastMember,+Version=1.5.0.0,+Culture=neutral,+PublicKeyToken=null"+was+chosen+because+it+was+primary+and+"FastMember,+Version=1.3.0.0,+Culture=neutral,+PublicKeyToken=null"+was+not.+(TaskId:19)
1>++++++References+which+depend+on+"FastMember,+Version=1.5.0.0,+Culture=neutral,+PublicKeyToken=null"+[C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll].+(TaskId:19)
1>++++++++++C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll+(TaskId:19)
1>++++++++++++Project+file+item+includes+which+caused+reference+"C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll".+(TaskId:19)
1>++++++++++++++FastMember,+Version=1.5.0.0,+Culture=neutral,+processorArchitecture=MSIL+(TaskId:19)
1>++++++References+which+depend+on+"FastMember,+Version=1.3.0.0,+Culture=neutral,+PublicKeyToken=null"+[].+(TaskId:19)
1>++++++++++C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll+(TaskId:19)
1>++++++++++++Project+file+item+includes+which+caused+reference+"C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll".+(TaskId:19)
1>++++++++++++++ClosedXML,+Version=0.94.2.0,+Culture=neutral,+processorArchitecture=MSIL+(TaskId:19)|code-block|syntax|javascript|3163114|请注意，Project+file+item+includes+which+caused+reference+"C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll"|3163115|ClosedXML.dll来自ClosedXML+NuGet，它依赖于FastMember.dll+1.3.0.0。最重要的是，项目中还有FastMember+Nuget，它有FastMember.dll+1.5.0.0。不匹配！|3163116|我已经卸载了ClosedXML+&+FastMember+NuGets，因为我有绑定重定向，并且刚刚安装了修复该问题的最新版本的ClosedXML！|3163117|entityMap^0|2K|E|0|F|2M|34|6|3G|S|0|0|4|49|0|0|D|F|9|Z|M|1X|A|2G|M|0|6|9|I|A|1S|9|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|T|$]]

I just spent sometime debugging the same issue. Note, that issue might not be between different projects, but actually between several references in one project that depend on different versions of the same dll/assembly. In my case, issue was reference <code>FastMember.dll</code> versions mismatch that comes from two different NuGet packages in a single project. When I was given a project, it would not compile because NuGet packages were missing and VS refused to restore missing packages. Through the NuGet menu, I manually update all the NuGets to the latest version, that is when the warning appeared. 

In Visual Studio <code>Tools &gt; Options &gt; Build and Run &gt; MSBuld Project build output verbosity: (set to) Diagnostics.</code> Look for the line(s) <code>There was a conflict between</code> in the <code>Output</code> window. Below is the part of output that I got:

<pre><code>1&gt; There was a conflict between "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" and "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null". (TaskId:19)
1&gt; "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" was chosen because it was primary and "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null" was not. (TaskId:19)
1&gt; References which depend on "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" [C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll]. (TaskId:19)
1&gt; C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll (TaskId:19)
1&gt; Project file item includes which caused reference "C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll". (TaskId:19)
1&gt; FastMember, Version=1.5.0.0, Culture=neutral, processorArchitecture=MSIL (TaskId:19)
1&gt; References which depend on "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null" []. (TaskId:19)
1&gt; C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll (TaskId:19)
1&gt; Project file item includes which caused reference "C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll". (TaskId:19)
1&gt; ClosedXML, Version=0.94.2.0, Culture=neutral, processorArchitecture=MSIL (TaskId:19)
</code></pre>

Notice, that <code>Project file item includes which caused reference "C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll"</code>

<code>ClosedXML.dll</code> comes from <code>ClosedXML</code> NuGet and it depends on <code>FastMember.dll 1.3.0.0</code>. On top of it, there is also <code>FastMember</code> Nuget in the project, and it has <code>FastMember.dll 1.5.0.0</code>. Mismatch ! 

I have uninstalled <code>ClosedXML</code> &amp; <code>FastMember</code> NuGets, because I had binding redirect and installed just latest version of <code>ClosedXML</code> That fixed the issue !

blocks|key|367415|text|这就是解决方案，.NET+Core3.0风格：https://github.com/HTD/ref-check|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|367416|当你发现什么是冲突时，也许你就能解决这些冲突。如果冲突的引用来自其他包，那么您要么运气不佳，要么需要使用源代码。|367417|在我的例子中，冲突的包通常是我自己的，所以我可以修复依赖问题并重新发布它们。|367418|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/HTD/ref-check^0|N|W|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Here's the solution, .NET Core 3.0 style:
<a href="https://github.com/HTD/ref-check" rel="nofollow noreferrer">https://github.com/HTD/ref-check</a>

When you find what conflicts, maybe you would be able to resolve the conflicts.
If the conflicting references are from other packages, you either out of luck, or you need to use sources instead.

In my case, the packages conflicting are often of my own, so I can fix dependency problems and republish them.

blocks|key|3375949|text|我也有同样的问题。在项目的'obj‘文件夹中，我将文件夹'Debug’重命名为'Debug_OLD‘并重新构建。一个新的'Debug‘文件夹被自动构建，这个问题就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3375950|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem. In the project's 'obj' folder I renamed the folder 'Debug' to 'Debug_OLD' and rebuilt. A new 'Debug' folder was built automatically, and the problem went away.

I am currently developing a .NET application, which consists of 20 projects. Some of those projects are compiled using .NET 3.5, some others are still .NET 2.0 projects (so far no problem).
The problem is that if I include an external component I always get the following warning:
<blockquote>
Found conflicts between different versions of the same dependent assembly.
</blockquote>
What exactly does this warning mean and is there maybe a possibility to exclude this warning (like using #pragma disable in the source code files)?

Warning: Found conflicts between different versions of the same dependent assembly

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我目前正在开发一个由20个项目组成的.NET应用程序。其中一些项目是使用.NET 3.5编译的，其他一些仍然是.NET 2.0项目(到目前为止没有问题)。问题是，如果我包含一个外部组件，我总是得到以下警告：发现同一依赖程序集的不同版本之间存在冲突。这个警告到底是什么意思，有没有可能排除这个警告(就像在源代码文件中使用#...

问警告:发现同一依赖程序集的不同版本之间存在冲突
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问警告:发现同一依赖程序集的不同版本之间存在冲突EN