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 portability rule: Use Only API from Targeted Framework.  This rule will fire when…

11

What happened to the download and documentation of FxCop 1.35?

Update: You can now download FxCop 1.35 directly from MSDN Code Gallery.  As you many you have well noticed, GotDotNet was officially retired last month now that the last of its functionality was superceded by MSDN Code Gallery. Unfortunately, at the same time, the FxCop team page, the download for FxCop 1.35 and the rule documentation was…

9

Try the Code Analysis Rule Sets Feature in the November "Rosario" November 2007 CTP

We have a great new feature that we are previewing in Microsoft® Visual Studio® Team System code name “Rosario” November 2007 CTP.  This feature allows you to select pre-defined sets of rules to configure code analysis as well as define your own.  To access this feature right click on a project and choose "Properties" then…

2

FxCop 1.36 Beta Released!

I’m pleased to announce that we’ve released a beta of the next version of FxCop. This release has a number of changes since FxCop 1.35, including, but not limited to, the following: 200+ bug fixes that reduce noise, missing analysis and rule crashes Support for analyzing anonymous methods and lambda expressions New option for skipping…

22

Visual Studio ‘Orcas’ Beta 1 Released!

If you’ve been living under a rock (or just distracted by this Silverlight thingy), you might have missed that we’ve released Beta 1 of Visual Studio ‘Orcas’. This release include a number of changes to Code Analysis when compared to Visual Studio 2005, including Code Metrics, generated code improvements, new rules, among other things. Beta 1 (for our…

0

After upgrading to Service Pack 1, the error ‘CA0055: Could not load [AssemblyName]’ occurs when running Code Analysis

We’ve been hearing a few reports of the following errors being output to the Error List after upgrading to Visual Studio 2005 Service Pack 1 (SP1): CA0055 : Could not load [AssemblyName].CA0052 : No targets were selected. If you look at the [AssemblyName].CodeAnalysisLog.xml file within your output folder, it may have contents similar to the following:         <?xml…

1

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 production machine as this will likely break Visual Studio 2005 when uninstalled. Besides the…

9

Do yourself a favor; install Visual Studio SP1 now

While this may be old news to some, we’ve had a few reports recently of bugs that were already fixed in Visual Studio Service Pack 1, so it appears that not everyone is running it. We fixed over 30+ bugs ourselves in Managed Code Analysis, so if you haven’t installed it yet, set aside some time and install…

2

Visual Studio 2005 SP1 Bug Fixes

Following Brian Harry’s lead and transparency, below is list of Managed Code Analysis fixes that made it into Visual Studio 2005 Service Pack 1.  Analysis FxCop reporting CA1811 on private const, while const is being used in code. Microsoft.VisualBasic.ComClassAttribute cause VB.NET compiler to generate code that doesn’t comply with design rules and gets noisy in FxCop…

3

FAQ: Why is FxCop 1.32 not available for download? [David Kean]

Update: While SharePoint Portal Server 2003 will not run side-by-side with .NET 2.0, SharePoint Portal Server 2003 SP2 will. For more information, see: http://support.microsoft.com/kb/907763. We have had a lot of users contacting us since we released FxCop 1.35, asking for a link to be able to download a copy of FxCop 1.32. There appears to be some…

11