In revision 3506, SharpDevelop 3.0 got improved support for code analysis using FxCop 1.36.

There were some bugs fixed that were related to the suppress message command - it was working only with FxCop 1.35, but even there couldn't suppress messages for static constructors and explicitly implemented interface members.

Using this command inserts a SuppressMessageAttribute in the code:

A new feature is support for custom dictionaries for the FxCop spell checker. Instead of suppressing tons of spelling messages, you can simply add a new xml file to your project with content like this:

<?xml version="1.0"?>
<Dictionary>
  <Words>
    <Recognized>
      <!-- add words specific to your application here -->
      <Word>Uncollapse</Word>
    </Recognized>
    <Unrecognized>
      <!-- Disable Lineup as a single word - LineUp is the spelling used in WPF -->
      <Word>Lineup</Word>
    </Unrecognized>
    <Deprecated>
      <!-- Use this section to deprecate terms -->
      <Term PreferredAlternate="Best">Bestest</Term>
    </Deprecated>
  </Words>
  <Acronyms>
    <CasingExceptions>
      <!-- Use this section to tell FxCop the correct casing of acronyms. -->
      <Acronym>WiX</Acronym>
    </CasingExceptions>
  </Acronyms>
</Dictionary>

And then set the file's build action to "CodeAnalysisDictionary" (this build action does not appear in the drop down, you'll have to type it in).