问题描述
我正在我对FxCop的DLL和它返回问题的形象在这里看到（这也抱怨System.Windows.Browser和System.Core程序，版本相同）：
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):
我已经告诉FxCop的搜索GAC，这是没有帮助。我必须在我的项目System.Runtime.Serialization引用，但它显示为4.0.0.0版本。我没有看到该文件的任何地方这一特定版本。
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.
虽然我可以跳过这意味着，当我使用的FxCop集成在Visual Studio中，我不知道会发生什么，如果我试图融入一个自动构建失败。
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.
推荐答案
BCL的DLL与2.0.5.0版本的Silverlight 4中，您presumably没有您的开发机器上安装的一部分。既然你是presumably使得没有用的Esri.ArgGIS.Client.dll总成针对Silverlight的零件，你很可能忽略了警告。
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.
似乎有关于这一问题的悬而未决的问题的FxCop的集成，所以你有三个基本的选择：
There seems to be an open issue for FxCop Integrator regarding this problem, so you have three basic choices:
- 在保持事物，是希望无视这些警告的选项将在集成的FxCop合理很快出台，
- 在停止使用的FxCop集成商，或者
- 在安装Silverlight 4。
有关自动化生成，其行为将取决于您的构建平台。而不是试图猜测一个自动生成可能会发生什么，你为什么不继续前进，并尝试呢？
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?
这篇关于FxCop的分析没有找到间接引用的程序 - GAC问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！