Static Analysis Updated MSOCAF for Visual Studio Code Analysis rules 2 years ago I worked on a huge SharePoint project where we had to run the MSOCAF wizard before deployment to the production environment. And of course, every time a few rules triggered that caused huge rework efforts. So I ended up recompiling the FxCop 1.36 rules that ship
Static Analysis FxCopContrib Alpha for Visual Studio 2012 I've just ported, fixed, compiled and released a version of my FxCopContrib library that should work under Visual Studio 2012 and Team Build 2012 [http://fxcopcontrib.codeplex.com/releases/view/100250]. The following rules are included: * Performance * FxC1801:DoNotUseParseAndToStringToConvertTypes [http://fxcopcontrib.codeplex.com/wikipage?title=DoNotUseParseAndTostringToConvertTypes&referringTitle=
Static Analysis Using existing Code Analysis Rules with TFS 11 beta Last week I explained how to get the Check-in policies from TFS 2010 working with TFS 11 [https://jessehouwing.net/visual-studio-2012-use-tfvc-checkin-policy-from-2010] , today I'll demonstrate how you can modify the configuration of Visual Studio 11 to allow it to run your custom Code Analysis rules without any modifications or
Static Analysis FxCopContrib project and DoNotIgnoreResultOfImmutableMethods custom rule Already a month ago I needed a place to store the code of the FxCop rules I was working on. I ended up at Codeplex, not only because they offer native TFS integration, but also because I hope others will join in on the effort. As of this moment, the
Static Analysis Have your Custom CodeAnalysis rule integrate properly with Visual Studio After porting the MSOCAF rules to FxCop 10, I noticed that you can't use the "Suppress in Source" option. Only the option "Suppress in Project suppression file" is available. Another problem with the global suppression is that it isn't scoped to a
Static Analysis MSOCAF rules As you might have read previously, I've been trying to incorporate MSOCAF directly in both Visual Studio 2010 and Team Build. The simplest solution would be to code up an msbuild task and put those in a target and reference that target in all project files. I know
Static Analysis Run MSOCAF in Visual Studio and on the build server UPDATE (1st of November 2011): I've since uploaded the re-targetted MSOCAF rules to CodePlex [http://fxcopcontrib.codeplex.com/SourceControl/changeset/view/3099]and I've applied a few fixes to prevent CodeAnalysis from crashing under certain conditions [https://jessehouwing.net/visual-studio-code-analaysis-msocaf-rules]. They're not part of
