Doing SharePoint development and a fan of FxCop for code analysis?
Make sure you have these set of SharePoint specific rules added:
It currently supports 19 different rules, most of them related to IDisposeable-patterns.
Continually running FxCop agaist your code during development (see this post on how to integrate it into Visual Studio) and prior release running SPDisposeCheker on all assemblies should prevent you from hitting most memory leak issues (and as a bonus you will discover other possible issues in your code that FxCop points out)
Another brain dump on my encounters during the numerous sessions of code
ripping at the .NET reef...
Aloha
Showing posts with label FxCop. Show all posts
Showing posts with label FxCop. Show all posts
Tuesday, March 30, 2010
Integrate FxCop 1.36 and VS 2008 Professional
Why Microsoft did not include the Code Analysis feature of Visual Studio 2008 Team System in Visual Studio 2008 Professional is a mystery to me, but here's a good article showing how it can be solved:
Personally I prefer using the FxCop.exe instead of FxCopCmd.exe and displaying the result to the output window in Visual Studio since it gives you a way better overview the issues.
(I always start by sorting them in Certainty order)
Here's what the settings should look like
Personally I prefer using the FxCop.exe instead of FxCopCmd.exe and displaying the result to the output window in Visual Studio since it gives you a way better overview the issues.
(I always start by sorting them in Certainty order)
Here's what the settings should look like

Subscribe to:
Posts (Atom)