I just came across this post by Travis Illig, one of the Subtext developers, that brings up an interesting issue with FxCop 1.35. Apparently, FxCop 1.35 uses the Office 2003 spell checker for the spelling rules. If you don’t have Office 2003 (and it must be Office 2003) installed, the spell check rules will fail. Travis isn’t the first person to document this problem.
This problem is known and will be fixed in newer versions of FxCop. Visual Studio 2008 code analysis tools have spelling rules built in and support custom dictionaries, but that will only help if you have one of the more expensive Team System editions of Visual Studio. FxCop 1.36, which is available in beta, also ships with the spell checker built in so you don’t need to have Office installed.