FxCop 分析未找到间接引用的程序集 - GAC 问题？
我正在针对 FxCop 运行我的 DLL，它返回问题，如图所示（它还抱怨 System.Windows.Browser 和 System.Core，相同版本）：
我已告诉 FxCop 搜索 GAC，但没有帮助。我的项目中确实引用了 System.Runtime.Serialization，但它显示为版本 4.0.0.0。我在任何地方都没有看到该文件的特定版本。
虽然我可以跳过它，但这意味着当我在 Visual Studio 中使用 FxCop Integrator 时它会失败，并且我不知道如果我尝试集成到自动构建中会发生什么。
但更重要的是，我很好奇你如何解决它，因为我不喜欢不理解出了什么问题。
I am running my DLL against FxCop and it is returning problems as seen in the image here (It also complains about System.Windows.Browser and System.Core, same versions):
I have told FxCop to search the GAC and it isn't helping. I do have System.Runtime.Serialization referenced in my project but it is showing as version 4.0.0.0. I do not see this particular version of the file anywhere.
Although I can skip it means it fails when I use FxCop Integrator in Visual Studio and I don't know what would happen if I tried to integrate into a automatic build.
But more to the point I am curious as to how you fix it as I don't like not understanding whats wrong.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
版本 2.0.5.0 的 BCL DLL 是 Silverlight 4 的一部分，您可能尚未将其安装在您的开发计算机上。由于您可能没有使用面向 Silverlight 的 Esri.ArgGIS.Client.dll 程序集的部分，因此您可以安全地忽略该警告。
关于此问题，FxCop Integrator 似乎存在一个未解决的问题，因此您有三个基本选择：
对于自动构建，行为将取决于您的构建平台。与其尝试猜测自动构建中可能会发生什么，为什么不继续尝试呢？
BCL DLLs with version 2.0.5.0 are part of Silverlight 4, which you presumably have not installed on your dev machine. Since you are presumably making no use of the parts of the Esri.ArgGIS.Client.dll assembly that target Silverlight, you could probably safely ignore the warning.
There seems to be an open issue for FxCop Integrator regarding this problem, so you have three basic choices:
For automated builds, the behaviour will depend on your build platform. Instead of trying to guess what might happen in an automatic build, why don't you go ahead and try it?
请看一下这个答案：https://stackoverflow.com/a/20799480/698
您可能仍在使用FxCop 10.0 不使用 PCL 处理这种情况。
当我切换到使用 VS.NET 2012 或 VS.NET 2013 FxCop 二进制文件后，它再次工作。
您在问题中包含了屏幕截图。不幸的是，FxCop11和FxCop12没有附带UI版本（因为它集成到VS.NET中）
Please take a look at this answer: https://stackoverflow.com/a/20799480/698
You might still be using FxCop 10.0, which doesn't handle this situation with the PCL.
Once I switched to using either the VS.NET 2012 or VS.NET 2013 FxCop binaries, it worked again.
You included a screenshot in the question. Unfortunately, FxCop11 and FxCop12 do not come with a UI version (since it is integrated into VS.NET)