Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Custom Rules » FxCop   (RSS)

Fun with Code Analysis Rule Sets

Two weeks ago, I introduced you to Visual Studio 2010 September '08 CTP (Community Technology Preview). This CTP is available as a Virtual PC (VPC) image which can be downloaded at http://go.microsoft.com/fwlink/?LinkId=129231 . The goal of the Community

Tutorial on writing your own Code Analysis rule

Jason Kresowaty has posted a great tutorial on writing Code Analysis/FxCop rules . He also spends time on explaining parts of the Introspection API, including the different nodes and their relationship to each other. It's a great read, even if you've

What kind of custom rules do you want to write?

Our excellent program manager, Joe Rohde, is trying to gather information on the kinds of custom rules customers want to write. I am a program manager for our Code Analysis system. I want to know what kind of custom rules you would like to write. Ignore

FAQ: How do I debug a custom rule?

While writing your custom rule, you will likely come across a need to debug it and work out why it's behaving in a particular manner. Debugging within FxCop Debugging a custom rule within the FxCop UI is actually quite easy. To do so, simply: Open the

Dealing with a Code Analysis backlog?

Nicole Calinoiu has started a (what I hope to be long) series on introducing Code Analysis (FxCop in particular) to your team. Her first couple of posts are absolute rippers , check them out: FxCop and the big, bad backlog FxCop backlogs: Some rules for

FAQ: How do I get the SourceContext for a local?

I want to fire on the naming of a local, however, whenever I pass the local to the Problem constructor, the source information for the method is always used. How do I get FxCop/Code Analysis to use the source information for the local instead? Because

FAQ: Can I create custom rules that target both Visual Studio and FxCop? [David Kean]

I have users using both Visual Studio and FxCop, and I want to create custom rules that run on both. Is this possible? Although in the future we do plan on making it easier to move custom rules between Visual Studio and FxCop, currently you must recompile
 
Page view tracker