Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Visual Studio 2... » 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 | 9 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 | 10 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

$(CodeAnalysisTreatWarningAsErrors) 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
 
Page view tracker