Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Configuration   (RSS)
Thursday, November 15, 2007 11:54 PM

Code Metrics Customization

A number of people have asked: Is there a way to customize the existing code metrics or add additional ones? The simple answer at this time is No.  There are no extension points or customizations available at this time for code metrics.  This
Posted by conorm | 10 Comments
Thursday, September 20, 2007 7:00 AM

New for Visual Studio 2008 - Code Analysis Policy improvements

One not very well known feature that lights up when connected to a Team Foundation Server, is the ability to enforce that Code Analysis be run before every check-in. Called a Code Analysis Policy , this feature allows your team to find and fix Code Analysis
Posted by David M. Kean | 11 Comments
Monday, August 20, 2007 7:00 AM

New for Visual Studio 2008 - Custom Dictionaries

Once you turn on the new spelling rules that we've added to Visual Studio 2008, you will want to start to customize the words that it fires on; this is where the new custom dictionary support comes in. A custom dictionary in its basic form, similar to
Posted by David M. Kean | 11 Comments
Sunday, August 12, 2007 7:00 AM

New for Visual Studio 2008 - Spelling rules

Surprisingly, one the biggest requests for Code Analysis in Visual Studio 2005 was to include the spelling rules that shipped with the FxCop standalone. We had Microsoft consultants tell us that they actually had trouble moving some customers from FxCop
Posted by David M. Kean | 13 Comments
Wednesday, August 08, 2007 8:00 AM

$(CodeAnalysisTreatWarningsAsErrors) MSBuild property

For Visual Studio 2008, we have added a new MSBuild property that allows you to easily treat all Code Analysis warnings as build errors. This can be useful for example, if you want to force that any firing of a Code Analysis rule to break the build during
Posted by David M. Kean | 2 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
Saturday, February 24, 2007 8:00 AM

FAQ: How do I run FxCop during a post-build event?

A little known feature of FxCop (in particular FxCopCmd.exe) is its ability to be integrated into the build process within Visual Studio. Although not a replacement for the Code Analysis functionality available within both Visual Studio Team Edition for
Posted by David M. Kean | 3 Comments
Attachment(s): VSConsoleOutput.xsl
Thursday, December 28, 2006 9:00 AM

FAQ: What is the GlobalSuppressions.cs/GlobalSuppressions.vb file and why is it needed? Is it possible to change the name of this file? [David Kean]

I've noticed that Code Analysis sometimes places suppressions in a file called GlobalSuppression.cs (GlobalSuppressions.vb in Visual Basic). Why this is file needed and it is possible to change its name? What is this file? When you right-click on a warning
Posted by David M. Kean | 1 Comments
Thursday, November 16, 2006 9:51 AM

FAQ: How do I share Managed Code Analysis rule settings over multiple projects? [David Kean]

If your team has a minbar of Managed Code Analysis rules that must be explicitly fixed or suppressed, it is possible to share the Managed Code Analysis rule settings over multiple MSBuild projects (.csproj, .vbproj). To share the minbar between multiple
Posted by David M. Kean | 9 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
Tuesday, April 04, 2006 5:45 PM

FAQ: How do I indicate to DoNotDeclareReadOnlyMutableReferenceTypes that a type is immutable? [David Kean]

DoNotDeclareReadOnlyMutableReferenceTypes is a rule that checks for visible read-only fields that are mutable reference types (classes). A mutable type is a type whose instance data can be changed once it has been constructed. For example, the following
Posted by David M. Kean | 2 Comments
 
Page view tracker