js.every_“依赖项every.dll无法复制到运行目录，因为它将与依赖项发生冲突...-CSDN博客

js.every

This is always a lovely error to get:

这总是一个可爱的错误：

"The dependency whatever.dll cannot be copied to the run directory because it would conflict with the dependancy..."

“依赖项every.dll无法复制到运行目录，因为它将与依赖项冲突...”

And again, it all comes down to knowing the places to look. If you open up the .csproj (or .vbproj) files you'll often see something like:

再说一次，这全都取决于知道要看的地方。如果打开.csproj(或.vbproj)文件，您通常会看到类似以下内容的内容：

<Reference
Name = "Corillian.Voyager.Thingie"
AssemblyName = "Corillian.Voyager.Thingie"
HintPath = "..\..\..\build\bin\Corillian.Voyager.Thingie.dll"
/>

<参考名称=“ Corillian.Voyager.Thingie” AssemblyName =“ Corillian.Voyager.Thingie” HintPath =“ .. \ .. \ .. \ build \ bin \ Corillian.Voyager.Thingie.dll” />

And assume that the HintPath is the place that VS.NET looks to resolve the reference. But, it's only a hint to the IDE. Often you'll have a situation where a project builds fine on one machine but not other, then the real evil resides in a file that you don't (shouldn't) check into source control and share, the .csproj.user file. In that file you'll find something like:

并假定HintPath是VS.NET用来解析引用的地方。但是，这只是对IDE的提示。通常，您会遇到这样的情况：一个项目可以在一台计算机上正常运行，而不能在另一台计算机上正常运行，那么真正的弊端就位于一个您不(不应)检入源代码控制并共享.csproj.user文件的文件中。在该文件中，您将找到类似以下内容的内容：

<VisualStudioProject>
    <CSHARP LastOpenVersion = "7.10.3077" >
        <Build>
            <Settings ReferencePath = "C:\Dev\VoyagerThingie\source\lib\Voyager\; C:\Dev\VoyagerThingie\source\lib\log4net\; C:\Dev\VoyagerThingie\build\bin\" >

<VisualStudioProject> <CSHARP LastOpenVersion =“ 7.10.3077”> <内部版本> <Settings ReferencePath =“ C：\ Dev \ VoyagerThingie \ source \ lib \ Voyager \; C：\ Dev \ VoyagerThingie \ source \ lib \ log4net \; C：\ Dev \ VoyagerThingie \ build \ bin \”>

What tends to happen is that folks forget about these files, and as versions change schmutz can creep into these files. So, when debugging bizarre reference problems, remember to check out the .user file! (or delete it and build it up again)

人们往往会忘记这些文件，随着版本的更改，schmutz可能会渗入这些文件。因此，调试奇怪的参考问题时，请记住签出.user文件！ (或删除并重新构建)