In the June 2004 installment of the Bugslayer column, I introduced the amazing FxCop, which analyzes your .NET assemblies for errors and problems based on code that violates the .NET Design Guidelines. This month I'll continue my discussion of building useful and advanced rules that will ensure you're writing the best .NET code possible. I'll assume that you've used FxCop extensively and that you've read the June 2004 Bugslayer column so that you have the basics of rule development under your belt.
For this column, I'm going to dive deeper into building rules, concentrating on those that work directly with the Microsoft® intermediate language (MSIL) instructions in your methods. But first, I think it's best to describe the three rules I developed so you can follow what I did to build them.
|