Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Rules » FxCop   (RSS)

Fun with Code Analysis Rule Sets

Two weeks ago, I introduced you to Visual Studio 2010 September '08 CTP (Community Technology Preview). This CTP is available as a Virtual PC (VPC) image which can be downloaded at http://go.microsoft.com/fwlink/?LinkId=129231 . The goal of the Community

New Code Analysis Features in Visual Studio 2010 September '08 CTP

At this year's PDC, Microsoft released Visual Studio 2010 September '08 CTP (Community Technology Preview). This CTP is available as a Virtual PC (VPC) image which can be downloaded at http://go.microsoft.com/fwlink/?LinkId=129231 . The goal of the Community

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

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

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

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

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

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

FxCop 1.35 rule documentation now on MSDN Wiki [David Kean]

One thing you might notice from today when you fire up FxCop 1.35 , is that the rule URLs are now redirecting to the new MSDN Library Wiki as opposed to the old docs on GotDotNet. To see this in action, try the following: Open FxCop 1.35 Choose Windows
 
Page view tracker