NUnit 未能引用最小起订量，仅在项目中
我有一个测试组件。如果我将该测试程序集加载到 NUnit 中，所有测试都会成功。
如果我将该测试保存为项目，我就会开始收到 159 个引用 Moq 的错误。
项目文件看起来像这样
<NUnitProject>
<Settings activeconfig="Default" />
<Config name="Default" binpathtype="Auto">
<assembly path="My.Assembly.Name.dll" />
</Config>
</NUnitProject>
错误是
My.Test.Name:
System.IO.FileLoadException : Could not load file or assembly
'Moq, Version=4.0.812.4, Culture=neutral, PublicKeyToken=69f491c39445e920' or
one of its dependencies. The located assembly's manifest definition does not
match the assembly reference. (Exception from HRESULT: 0x80131040)
错误本身很公平。我们使用的是 NuGet 中的 v4.0.10827，因此您不会期望它找到 v4.0.812.4。问题是：为什么它要寻找这个，为什么只有当我使用 .nunit 项目文件时？
测试程序集没有引用旧版本，并且解决方案中没有其他程序集引用它。
I have a test assembly. If I load that test assembly into NUnit, all tests succeed.
If I then save that test as a project, I start getting 159 errors with a reference to Moq.
The project file looks like this
<NUnitProject>
<Settings activeconfig="Default" />
<Config name="Default" binpathtype="Auto">
<assembly path="My.Assembly.Name.dll" />
</Config>
</NUnitProject>
The error is
My.Test.Name:
System.IO.FileLoadException : Could not load file or assembly
'Moq, Version=4.0.812.4, Culture=neutral, PublicKeyToken=69f491c39445e920' or
one of its dependencies. The located assembly's manifest definition does not
match the assembly reference. (Exception from HRESULT: 0x80131040)
The error itself is fair enough. We're using v4.0.10827 from NuGet, so you wouldn't expect it to find v4.0.812.4. The question is: why is it looking for that, and why only when I use a .nunit project file?
The Test assembly is not referencing an older version, and no other assembly in the solution is referencing it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
尝试将 .nunit 项目文件重命名为 My.Assembly.Name.dll.nunit，我遇到 .nunit 项目问题，找不到被测程序集的 app.config 文件，这就是我解决该问题的方法。
Try to rename the .nunit project file to My.Assembly.Name.dll.nunit, I have issues with .nunit projects not finding app.config files for the assemblies under test and that's how I solved it.