Game Development Reference
Figure 13.2 Screen capture of the rules configuration tab.
Figure 13.3 Screen capture of the button that starts the analysis.
Both types are fairly subjective in nature, and many rule developers feel that it
would have made their lives a lot easier if Microsoft had just simplified the mes-
sage levels to errors, warnings, and informational messages.
Aside from the message level, you will notice that there are a few other statistics for
each violation. The fix category indicates whether or not your code will break if
the violation is resolved by itself. Breaking indicates that fixing the violation with-
out modifying the rest of your code will cause compilation errors, such as chang-
ing a property name referenced elsewhere. Nonbreaking indicates that fixing the
violation without modifying the rest of your code should still result in a success-
ful compilation, such as adding an attribute to a class definition. Figure 13.4 shows
the FxCop project window after an analysis has been performed.