There are lots of Code Analysis (FxCop) warnings.
有很多的代码分析(FxCop)警告。
New features included in FxCop 1.36 final release.
FxCop 1.36最终版中包含的新特性。
The recommendation from FxCop is to initialize static fields where they are declared.
FxCop建议在声明静态字段的位置对其进行初始化。
NOTE: If you already have FxCop 1.36 Beta 2 installed, uninstall it before installing FxCop 1.36.
注意:如果你先前已经安装了FxCop 1.36Beta2,在安装FxCop 1.36之前需要先卸载Beta 2。
While FXCop does offer a lot of analysis rules, not all of them are applicable to a given project.
FXCop确实提供了大量的分析规则,但并不是所有的都适合一个给定的项目。
FxCop can help you create better, more consistent code, but it cannot make up for poor application design or just plain poor programming.
FxCop可以帮助你创建更好的、更一致的代码,但它无法补偿低劣的应用程序设计或非常简单拙劣的编程。
Although we have guidance and FxCop rules that recommend always using overloads that take a StringComparison parameter, unaware developers often just use the default overloads.
虽然我们已经制定了编程指南以及FxCop规则,以建议开发者总是使用接受StringComparison参数的重载方法,但开发者总是不自觉地使用默认的重载方法。
FxCop is one of the tools that can be used to help create better applications by enabling you to examine an assembly and check it for compliance using a number of different rules.
FxCop是有助于创建更好的应用程序的工具之一,通过分析程序集,并使用许多不同的规则来检查它是否符合这些规则。
If you compile the classes in Figure 1 and run the resulting assembly through the FxCop tool, you will find that it produces a critical warning about the ExplicitConstructor class.
如果您编译图1中的类,然后通过FxCop工具运行得到的程序集时,就会发现它会生成一个关于explicitconstructor类的严重警告。
When an explicit type constructor is present, the compilers will not mark the type with beforefieldinit, and the precise timing restrictions lead to the performance drop hinted at by FxCop.
当存在显式类型构造函数时,编译器不会用beforefieldinit标记该类型,精确的计时限制会导致FxCop所暗示的性能下降。
When an explicit type constructor is present, the compilers will not mark the type with beforefieldinit, and the precise timing restrictions lead to the performance drop hinted at by FxCop.
当存在显式类型构造函数时,编译器不会用beforefieldinit标记该类型,精确的计时限制会导致FxCop所暗示的性能下降。
应用推荐