Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Tips and Tricks   (RSS)
Wednesday, January 02, 2008 8:10 PM

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
Posted by conorm | 10 Comments
Tuesday, May 08, 2007 8:00 AM

TIP: How to change the (Orcas) Managed Code Analysis naming/design rules to fire on internals

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 FxCop/Managed
Posted by David M. Kean | 1 Comments
Tuesday, January 30, 2007 8:00 AM

TIP: Scope the Code Analysis Policy to apply to specific source control paths/file types

On the forums, we have had posts from customers who want to customize their code analysis policy to skip certain file types such as .sql, docs etc. This is because the policy will block checkins even though code analysis doesn’t apply to those files.[
Posted by ravkaur | 1 Comments
Thursday, January 18, 2007 8:00 AM

TIP: Automatically generate Managed Code Analysis/FxCop suppressions

I see a lot of users attempting to hand code a SuppressMessageAttribute themselves. This can be error prone and is not needed when both Visual Studio and the standalone FxCop can automatically generate these for you. In Visual Studio 2005 Right-click
Posted by David M. Kean | 1 Comments
Friday, August 11, 2006 8:00 AM

TIP: How to quickly enable Code Analysis on multiple projects [David Kean]

Daniel Fisher has posted a entry on using a macro to quickly enable Code Analysis on multiple projects . The macro also allows you to apply the same rule selections across an entire solution. Thanks Daniel!
Posted by David M. Kean | 0 Comments
Tuesday, August 08, 2006 8:56 PM

TIP: How to change the FxCop naming/design rules to fire on internals [David Kean]

By default, the FxCop naming and design rules only fire on publicly visible types and members. There are a couple reasons for this: The .NET Framework Design Guidelines , which FxCop enforces, only contains guidelines for publicly visible API. What internal
Posted by David M. Kean | 4 Comments
Monday, June 12, 2006 10:53 PM

TIP: Get more information about a rule/warning within Visual Studio [David Kean]

Did you know you can get more information about a particular rule/warning within Visual Studio; including its description, information on how to fix it, whether or not it is considered a breaking change, when or when not to suppress it and code samples?
Posted by David M. Kean | 3 Comments
 
Page view tracker