Code Analysis Team Blog

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: ...

It appears that sometimes FxCop displays a link to the source line and file in the Message Details window and sometimes it doesn't. Why this inconsistent behavior? There are three usual reasons why this occurs: Source lookup is disabled. To turn...

A lecture on API design by Krzysztof Cwalina (the brains behind the Framewok Design Guidelines ) has been posted on the Research Channel . This class presents best practices for designing frameworks that are reusable object-oriented libraries. The...

A while ago I mentioned that FxCop (and hence Managed Code Analysis) naming and design rules only fire on publicly visible types and members. As you may recall, there were a couple of reason for this: The .NET Framework Design Guidelines , which...

If you've been living under a rock (or just distracted by this Silverlight thingy), you might have missed that we've released Beta 1 of Visual Studio 'Orcas' . This release include a number of changes to Code Analysis when compared to Visual Studio...

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...

We had two great chats last Friday . Thank-you to all that attended, I had a lot of fun. The following is a list of Code Analysis questions that were asked: Code Metrics DavidKean_MS (Moderator): Q: JeffBe: I'm very interested in the code...