Mapping between FxCop Rules and .NET Design Guidelines
Is it planned to implement a mapping between FxCop Rules and the "real" MSDN .NET Design Guidelines? (Could be a table on some web page or something in the FxCop CHM).
Regards
Micha
Is it planned to implement a mapping between FxCop Rules and the "real" MSDN .NET Design Guidelines? (Could be a table on some web page or something in the FxCop CHM).
Regards
Micha
We don't have any plans currently to put this information in the FxCop chm. Can you describe why it would be helpful to you? Maybe we're missing a good opportunity.
An example from the latest MSDN for Visual Studio 2005 which contradicts FxCop rules:
"If you are designing an application that needs to create its own exceptions, derive from the ApplicationException class."
Generally speaking, you should always run the Design and Naming rules. This is where we place content derived directly from the MS DG. Because we update FxCop more frequently than the DG, you can count on FxCop delivering the most recent and accurate thinking.
I'll post more re: this general subject soon.
Thanks for your comments.. and I totally agree, we need to push this content on the design guidelines out widely.. as you likely know I publish the content regularly on my blog (http://blogs.msdn.com/brada) and we did update the Design Guidelines docs on MSDN slightly with this content and we expect to update it even more as the UE team gets more cycles. Please keep giving us feedback on this! Oh, and BTW, Krys and I did the book as part of our jobs here at MS, so no royalties for us.. consider the book itself to be a community service.
Pushing content out more widely via blogs etc is a great way to communicate how thinking on the guidelines is evolving.
But really there needs to be a single authoritative source for the current "official" guidelines, and I think someone who has paid $10000+ for MSDN Premium with Team Suite should reasonably be able to expect the design guidelines for the integrated code analysis tool he has purchased to be included in the package, without the need to go out and buy a paper book.
I like that idea, too!
BTW: We're using VSTS RC1 as IDE recommendation. There's an integrated FxCop. But what version is it? And why can't I find some help about the Rules SDK? Is there some documentation available?
Custom rules development is an officially unsupported scenario, see the FAQ in this forum. Rules development will certainly be supported in the next VS release.