Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Rules   (RSS)
Monday, August 25, 2008 7:00 AM

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
Posted by David M. Kean | 1 Comments
Tuesday, August 19, 2008 9:11 PM

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
Posted by brettwo | 8 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
Thursday, August 09, 2007 7:00 AM

What rules do Microsoft have turned on internally?

I've recently received a few requests asking about the Code Analysis rules we run internally against Microsoft's own code. While it might come as a surprise, we do not actually run every single rule against our own binaries. There are many reasons for
Posted by David M. Kean | 19 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 03, 2007 8:00 AM

What resolutions or warnings need to provide more information?

One of things that we are doing for Orcas, is to basically do what we call a resolution scrub . This is where we print out every single possible resolution/warning and read over them to check for consistency, proper grammer and to see if they provide
Posted by David M. Kean | 9 Comments
Thursday, February 01, 2007 8:00 AM

How to Design Exception Hierarchies

Krzysztof Cwalina, owner of the Framework Design Guidelines , has written a great post on designing exception hierarchies . He gives a great overview on the different categories of exceptions, which are placed under two main buckets he calls usage and
Posted by David M. Kean | 0 Comments
Monday, January 22, 2007 8:00 AM

FAQ: What exception should I throw instead of the reserved exceptions that DoNotRaiseReservedExceptionTypes warns against?

Throwing a general exception type such as System.Exception or System.SystemException in a library or Framework forces consumers to catch all exceptions, including unknown exceptions that they do not know how to handle (see FAQ: Why does FxCop warn against
Posted by David M. Kean | 14 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
Sunday, January 14, 2007 8:00 AM

FAQ: How do I fix a violation of MovePInvokesToNativeMethodsClass?

MovePInvokesToNativeMethodsClass fires on P/Invokes (ie methods marked with DllImport) that are not members of one of the following classes; NativeMethods, SafeNativeMethods or UnsafeNativeMethods. For example, the following sample fires this warning.
Posted by David M. Kean | 1 Comments
Friday, January 12, 2007 8:00 AM

January Orcas CTP Released!

Update: A Virtual PC image is also available. We've just released the Visual Studio 'Orcas' - January CTP . This is the first of the side-by-side installable CTPs, however, before installing, please read the Release Notes and do not install this on a
Posted by David M. Kean | 9 Comments
Saturday, January 06, 2007 5:00 PM

And now back to your regularly scheduled FxCop documentation...

As a lot of you noticed, just before Christmas all of our rule documentation links broke from within FxCop. Unfortunately, due to the timing (and with the required people on holidays), we could not get this fixed as soon as we had hoped. However, as of
Posted by David M. Kean | 0 Comments
Wednesday, October 25, 2006 10:58 PM

How would you rate the usefulness of this content? [David Kean]

At Microsoft, we have a number of internal tools and websites that help improve our interaction with the community. One such site at our disposal is a tool that helps us browse feedback provided about MSDN Library topics. This feedback, which at times
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
More Posts Next page »
 
Page view tracker