As some of you may already know, the majority of the Developer Division is currently planning features to be included in the next version of Visual Studio (Orcas). As part of this planning phase, the Managed Code Analysis (FxCop) team is beginning to work with other teams around Microsoft to ensure that any customer facing code released in Orcas is Code Analysis clean.
We’re also asking for your help. If you’ve ever come across code that hasn’t passed Code Analysis whether that be generated by custom tools, compilers, MSDN Library examples, sample applications, templates, designers, articles or any other Microsoft produced code, we want to hear about it.
Blog about it, tell your colleagues, managers, friends, spouses (if they write code), mailing lists, forums and any other medium that you can think of that if they have ever come across code that made them say ‘Damn Microsoft, I wish they would follow their own guidelines’ – then the Code Analysis team wants to hear from them.
As an example of what kind of issues we are looking for, see the following Product Feedback Center bugs:
Prevent generated DSL code from producing FxCop warnings
Windows Service template Dispose method does not pass FxCop analysis
AssemblyInfo to be FxCop compliant by default
“exception” expansion code sniplet has incorrect “public” visibility for serialisation contructor. FxCop rule violation
You can either post your feedback via a comment below or by using this blog’s contact form.