FxCop 1.36 Beta Released!

MSDN Blog Postings » FxCop 1.36 Beta Released!

MSDN Blog Postings » FxCop 1.36 Beta Released! — Thu, 11 Oct 2007 00:22:41 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/10/10/fxcop-136-beta-released/

FxCop sigue vivo... ¡viva FxCop!

Jorge Serrano - MVP Visual Developer - Visual Basic — Thu, 11 Oct 2007 10:37:40 GMT

Microsoft ha publicado una nueva versión de FxCop en versión Beta 2, se trata de FxCop 1.36 Beta 2. La

Multithreading rules

Franck Jeannin — Thu, 11 Oct 2007 11:09:37 GMT

Can we expect anything on race condition detection in the future? What happened to the work on RaceTrack done by Microsoft Research back in 2004?! Can Spec# help?

FxCop 1.36 Beta available for download

Jan Schreuder on .Net — Thu, 11 Oct 2007 17:32:45 GMT

The Visual Studio Code Analysis Team Blog announces the release of FxCop 1.36 Beta.This new version contains

Izindaba #13

From the software development trenches — Fri, 12 Oct 2007 07:55:06 GMT

It is time for another weekly roundup of news that focuses on .NET, agile and general development related

FxCop 1.36 Beta 2 disponible

CoqBlog — Sat, 13 Oct 2007 00:14:28 GMT

Une version beta du prochain FxCop (la version standalone) est disponible . Il supporte l'analyse d'assemblies

re: FxCop 1.36 Beta Released!

Joe K — Sat, 13 Oct 2007 14:53:07 GMT

Does Code Analysis in Visual Studio 2008 have these improvements as well? I remember reading that Code Analysis got spell checking but not sure how directly FxCop and Visual Studio Code Analysis are related.

re: FxCop 1.36 Beta Released!

Scott Jones — Mon, 15 Oct 2007 23:39:49 GMT

How about some documentation on the diffs in the fxcop sdk between 1.35 & 1.36, for us custom rule authors? It appears that a lot of functionality in RuleUtilities was farmed out to other classes. In some cases, it's easy to find the new functionality. In other cases, not so much.

re: FxCop 1.36 Beta Released!

Scott Jones — Tue, 16 Oct 2007 02:50:06 GMT

I might also add that David Kean's custom rules no longer build with FxCop 1.36, due to all the breaking sdk changes.

New FxCop 1.36 beta 2 released

.NET slave — Tue, 23 Oct 2007 22:26:34 GMT

New FxCop 1.36 beta 2 released

re: FxCop 1.36 Beta Released!

Franck Jeannin — Thu, 25 Oct 2007 15:41:22 GMT

If you wonder why SuppressMessage works in FxCop 1.36/VS2008 and not in FxCop 1.35, notice the subtle difference in the syntax.

FxCop1.36/VS2008

[assembly: SuppressMessage("Microsoft.Performance", "CA1811:AvoidUncalledPrivateCode", Scope = "member", Target = "MyNamespace.MyClass.#MyMethod()")]

FxCop1.35

[assembly: SuppressMessage("Microsoft.Performance", "CA1811:AvoidUncalledPrivateCode", Scope = "member", Target = "MyNamespace.MyClass.MyMethod():System.Void")]

When in doubt, you can use the right click/Copy As->SuppressMessage command in FxCop to place the correct syntax in the clipboard.

re: FxCop 1.36 Beta Released!

MikeGH — Mon, 29 Oct 2007 15:30:48 GMT

Is there any plans to add support for drop it-in over the fxcopcmd that VS2005 Code Analysis uses...

There appears to be an issue with parsing the rules path atm...

re: FxCop 1.36 Beta Released!

Manu — Thu, 01 Nov 2007 10:35:03 GMT

Is there any way to suppress the same FXCop warning that is being reported multiple times with a SuppressMessage attribute?

re: FxCop 1.36 Beta Released!

Eugenez — Thu, 08 Nov 2007 03:45:35 GMT

Dear team,

Thank you for the release; but could you provide list of deprecated rules?

I have found that the following at least are different:

- Performance rules, DisposeMethodsShouldCallSuppressFinalize missing

- Performance rules, DoNotConcatenateStringsInsideLoops missing

- Usage rules, DoNotMarkEnumsWithFlags does not seem to work anymore

- Usage rules, NonConstantFieldsShouldNotBeVisible does not seem to work anymore

Am wating for the answer as I kinda hated ploughing through the rules trying to figure out what works and what does not.

Thanks, Eugene

re: FxCop 1.36 Beta Released!

Colin Bowern — Thu, 08 Nov 2007 20:27:02 GMT

How does this related to the pending VS2008 release? Can we upgrade the out-of-the-box code analysis in VS2005/2008 with the latest fxcop?

re: FxCop 1.36 Beta Released!

David M. Kean — Thu, 08 Nov 2007 20:39:01 GMT

Mike: There will be no support to drop it over the version of FxCop in Visual Studio 2005. There have been changes to the output format that make it incompatible.

Manu: Typically no. SuppressMessage only suppresses an instance of 1 warning. If you want to suppress it multiple times, consider turning the rule off.

Eugenez: DisposeMethodsShouldCallSuppressFinalize has been moved and renamed to Usage\CallGCSuppressFinalizeCorrectly.

The following rules have been removed (most of them were part of our data flow engine that has been discontinued - we will be replacing them in a future version):

ValidateArgumentsOfPublicMethods

DoNotPassLiteralsAsLocalizedParameters

AvoidUnnecessaryStringCreation

DoNotCallPropertiesThatCloneValuesInLoops

DoNotConcatenateStringsInsideLoops

ReviewSqlQueriesForSecurityVulnerabilities

AssembliesShouldDeclareMinimumSecurity

DisposeMethodsShouldCallBaseClassDispose

ProvideCorrectArgumentsToFormattingMethods

The following rules have been renamed/merged into other rules:

LongAcronymsShouldBePascalCased

ShortAcronymsShouldBeUppercase

AvoidTypeNamesInParameters

AvoidLanguageSpecificTypeNamesInParameters

AvoidTypeNamesInParameters

SecureGetObjectDataOverrides

DoNotRaiseExceptionsInFilterBlocks

With regards to the two rules that don't work, can you head over the FxCop forum and provide us a repro?

Colin: You will not be able to update 2005 with the latest version and will we have made changes to allow 2008 to be updated - there is no need, it comes with the latest analysis (and actually has more analysis than FxCop).

re: FxCop 1.36 Beta Released!

Eli Allen — Mon, 10 Dec 2007 22:15:19 GMT

While 2008 may at present be up to date with fxcop rules I'm going to guess that new rules will be made in the future so it will still be useful to be able to update the fxcop rules.

re: FxCop 1.36 Beta Released!

David M. Kean — Tue, 11 Dec 2007 23:01:50 GMT

Eli: Rules that are in Visual Studio 2008 and not in FxCop 1.36 will never make it into later in a future version. Visual Studio will always remain superset of what is available in the free FxCop.

re: FxCop 1.36 Beta Released!

Denis — Wed, 12 Dec 2007 00:40:23 GMT

What is most likely time of production release of FxCop 1.36?

re: FxCop 1.36 Beta Released!

David M. Kean — Wed, 12 Dec 2007 00:43:30 GMT

Denis: We haven't announced the exact date, however, it will likely be at the start of next year.

FxCop 1.35 Spell Checking Uses Office 2003

Paraesthesia — Wed, 19 Dec 2007 22:28:25 GMT

FxCop 1.35 Spell Checking Uses Office 2003

How to: Setup a solution for developing FXCop/Code Analysis custom rules.

Driven by Development — Thu, 17 Apr 2008 21:06:03 GMT

This post is not about creating custom rules for FxCop because there are already some resources on the