Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule

I've just published a post over my blog about a new feature we added for Visual Studio 2008 SP1 and FxCop 1.36. New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule

FxCop 1.36 Released!

We are pleased to announce that we've released the next version of FxCop . This release has a number of changes since FxCop 1.36 Beta 2, including, but not limited to, the following: Bug fixes that reduce noise, missing analysis and rule crashes. New

David Kean's new blog

For those that are interested, I've just started a new personal blog, Dave's Box , where I will be talking about FxCop, Framework Design Guidelines, and the recently announced Managed Extensibility Framework . I've just posted a couple of posts detailing

FxCop 1.35 now available (again) for download

We've just uploaded FxCop 1.35 to MSDN Code Gallery after we lost our home on GotDotNet - this is for those teams that either do not want to or just aren't ready to upgrade to FxCop 1.36 Beta . For those that are already using FxCop 1.35, you'll probably

FAQ: How do I prevent FxCop 1.36 from firing warnings against generated code?

I've upgraded from FxCop 1.35 to 1.36 and now FxCop has started to fire warnings against typed DataSets and other generated code. How do I turn this off? The reason this is occurring is because we changed the way that FxCop analyzed generated code. Whereas
Posted by David M. Kean | 5 Comments
Filed under: , ,

What happened to the download and documentation of FxCop 1.35?

Update: You can now download FxCop 1.35 directly from MSDN Code Gallery . As you many you have well noticed, GotDotNet was officially retired last month now that the last of its functionality was superceded by MSDN Code Gallery . Unfortunately, at the
Posted by David M. Kean | 9 Comments

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 do you want to see in the second edition of Framework Design Guidelines?

Krzysztof and Brad have announced they are working on the second edition of the awesome Framework Design Guidelines and are looking for feedback on what they should put in it. For those that don't know, a lot of our Code Analysis rules are based on the

FAQ: Which Code Analysis rules shipped in which version?

In response to a lot of recent requests, we've put together a complete list of rules that shipped in the different versions of Visual Studio Code Analysis and FxCop. Attached is an Excel worksheet providing this information for Visual Studio 2005, Visual

Reporting Code Analysis Defect Counts

Code analysis defect counts are available in the cube that is part of the TFS Data Warehouse . This post shows you how to hook up Excel to show code analysis counts in a pivot table . First off you need to connect Excel up to the data warehouse that has

Come chat with the Code Analysis team tomorrow

Join members of the Visual Studio Team System product group to discuss features available in Team Foundation Server, Team Suite, Architecture Edition, Development Edition, Database Edition, and Test Edition. In addition, discuss what's new for these editions

Try the Code Analysis Rule Sets Feature in the November "Rosario" November 2007 CTP

We have a great new feature that we are previewing in Microsoft® Visual Studio® Team System code name “Rosario” November 2007 CTP .  This feature allows you to select pre-defined sets of rules to configure code analysis as well

Positioning Code Metrics to Management

Another question that is coming up is: How can (or should) code metrics be presented to management ? My view is that in all cases the metrics are something that can help make decisions around focus and prioritization. Management should be made aware of

Maintainability Index Range and Meaning

Another question: The maintainability index has been re-set to lie between 0 and 100. How and why was this done? The metric originally was calculated as follows (based on the work in Carnegie Mellon University although we modified the Halstead Volume

Code Metrics as Check-in Policy

This is the first in a series of posts around questions I am getting asked related to code metrics. One question that is coming up is: Can a check-in policy be defined based on code metrics in TFS? Well, code metrics itself does not have a check-in policy
More Posts Next page »
 
Page view tracker