FxCop 1.30 released [Jeffrey van Gogh]

Fantastic Improvement!

Craig Eddy — Mon, 29 Mar 2004 22:01:00 GMT

Great work guys. This version is awesome.

re: FxCop 1.30 released [Jeffrey van Gogh]

Douglas McClean — Mon, 29 Mar 2004 23:19:00 GMT

Excellent work :).

One minor feature request for next time: when a rule is violated by a parameter, the target information could be more helpful.

Example:
Target : "0" (IntrospectionTargetParameter)
Resolution : "Correct the capitalization of parameter name 'permissionID'
by changing 'ID' to 'Id'"

It would be helpful to know the name of the qualified name of the method that this is parameter 0 of.

re: FxCop 1.30 released [Jeffrey van Gogh]

AndrewSeven — Mon, 29 Mar 2004 23:30:00 GMT

Woohoo!

re: FxCop 1.30 released [Jeffrey van Gogh]

Jeffrey van Gogh — Mon, 29 Mar 2004 23:45:00 GMT

Douglas, good suggestion! We'll try to get it in our next release. A workaround for now is doubleclicking on the message to see the details.

An interesting feature in that dialog is that if you select the second tab called "message" and doubleclick on the treeview you see there, you can make FxCop jump to that item in the target treeview.

New Version of FxCop Released (1.30)

Steven Smith — Tue, 30 Mar 2004 07:26:00 GMT

re: FxCop 1.30 released [Jeffrey van Gogh]

SSW Code Auditor — Tue, 30 Mar 2004 13:26:00 GMT

We are using SSW Code Auditor at the moment. Is FxCop better any better? Can I write my own rules?

KKJ
FarEast

FxCop 1.30 released

SiM Weblog — Tue, 30 Mar 2004 19:01:00 GMT

re: FxCop 1.30 released [Jeffrey van Gogh]

Drew Noakes — Thu, 01 Apr 2004 09:27:00 GMT

Fantastic. Thanks for your hard work on this, and for including the feature I requested (next/prev buttons on message dialog form). I have some more suggestions, though will post them on the GDN site.

Congratulations again!

FxCop 1.30

Vinod Kumar's Blog — Thu, 01 Apr 2004 14:04:00 GMT

Some Links #18

Julien Cheyssial's Blog (FR) — Thu, 01 Apr 2004 21:44:00 GMT

FxCop 1.3 Is out.. and it rox!

Dana Epp's ramblings at the Sanctuary — Sat, 03 Apr 2004 02:33:00 GMT

OK. Kudos to the FxCop team. First off, I need to thank them for sending me this kewl t-shirt. Nice little Microsoft logoware with an FxCops twist. I appreciate it. Thanks Mike! Secondly... I installed the latest build(1.30) today and see that they fixed the biggest issue I had! It no longer locks my assemblies. So I now have FxCop running along side of Visual Studio! Next job is to figure some way to get it to execute on a post-build event so I can run it through FxCop after each major compile. And who says Microsoft doesn't always listen?...

FxCop 1.30 released

Thoemmi.NET — Thu, 15 Apr 2004 18:06:00 GMT

Maybe I', a little late, since it is more than two weeks ago.
Anyway, the FxCop team has released version...

re: FxCop 1.30 released [Jeffrey van Gogh]

Chris — Tue, 11 May 2004 08:16:00 GMT

The file locking stuff is really cool but the rest of the app has become really unstable in 1.30. The new version feels really fragile, the UI is much slower and the configuration files are not readable anymore. It also pops up exception and file not found dialogs for me all the time. I'm wondering... can you provide a Whidbey version of the old FxCop 1.2 version until all the issues with the new version are fixed? I also agree with Dana, command line build integration is still missing in 1.30. Why do I have to create those huge project files all the time?

re: FxCop 1.30 released [Jeffrey van Gogh]

Chris — Tue, 11 May 2004 08:21:00 GMT

In case you haven't seen this already: SharpDevelop now provides another guideline checking tool called "Assembly Analyzer" (full source code included).