Browse by Tags

Tagged Content List
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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 -> Rules Expand the Naming Rules...
  • Blog Post: FxCop 1.35 Released!

    We are pleased to announce the release of FxCop 1.35. Please visit http://www.gotdotnet.com/team/fxcop to download it. Changes since FxCop 1.32: FxCop now only runs on .NET Framework 2.0, however, it supports analyzing all versions of .NET Framework. Support for in source suppression...
  • Blog Post: Making it easier to move from FxCop to Visual Studio Code Analysis [Jeffrey van Gogh]

    We get frequently asked what the best way is for people to move from the standalone FxCop to VS Code Analysis. A hurdle in making the switch is the fact that people can no longer use the FxCop project file they created for their analysis. This will invalidate all the exclusions that were made previously...
  • Blog Post: FxCop 1.35 RC1 online

    Last week we had a push to fix many of the issues reported on the forum and include them in the FxCop 1.35 release. 32 bugs later, we have a release candidate ready. The code changes between FxCop 1.35 Beta 1 and RC 1 range from simple bugs such as updating the copyright notice, to as complicated...
  • Blog Post: Microsoft Visual Studio 2005 Team System announced @ Teched today [Jeffrey van Gogh]

    This morning @ Teched, Steve Ballmer announced “Microsoft Visual Studio 2005 Team System“. Definately something for users of both VS & FxCop to take a look at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvsent/html/vsts-dev.asp If you're @ Teched, don't forget...
  • Blog Post: FxCop 1.30 released [Jeffrey van Gogh]

    Hi All, We just released FxCop 1.30! Please visit http://www.gotdotnet.com/team/fxcop/ to download it. main features: -No more locks on assemblies or pdbs -Ability to resolve missing dependencies -Ability to analyze just about anything running just about anywhere -Analysis is now multi-threaded...
  • Blog Post: FxCop 1.30 on track for http://www.gotdotnet.com/team/fxcop release[Michael Fanning]

    Just a heads up that FxCop 1.30 testing is right on track and we expect to ship on http://www.gotdotnet.com/team/fxcop by the end of this month, March 2004, as expected!
  • Blog Post: What's In The New Version Of FxCop [Michael Fanning]

    As mentioned in previous blog and bulletin board posts, we’re in the final weeks of testing a new update to FxCop. This is a very significant update and I thought I’d post some information on what to expect in the release. No more locks on assemblies or pdbs FxCop uses a new,...
Page 1 of 1 (18 items)