New Version of FxCop

Hot Topic

TFS Extensibility Problem (Microsoft.VisualStudio.Currituck.Proxies.DataServices)
Visual Studio Team System - Requirements
[Team Explorer] Can't change user who connects to the TFServer
VSTS Server can't be connected by error"underlying connection closed"
Exclude a File from Source Control
How to resolve: Assemblies should have valid strong names
Differences between FxCop GUI and VS 2005
New Projects do not get retrieved on get latest version
I can no longer view the Team System Installation Guide.
vsmdi relationship to TestCase/TestMethods

VS Team System

Customizing Code Analysis
Error Publishing Test Result
How do I view all Pending Changes for other users
Multi Branches
TFS Warehouse errors
Workspace is already mapped problem
CSV Datasource can't be read after converting to C#
Initialize reference type static fields inline
MsTest command line publish code coverage
How to integrate other code analysis progress in Team Build

New Version of FxCop

Hi all,

Its been a month :), just kiding.

Is or will the new version be included in VS 2005 RC1 Or when will it be intergrated, because i would like to make some custom rules, but ofcourse i want to do it in the new version.

Greetings.

Answer this question

New Version of FxCop

  • James Rosenvall

    Ok thanks, i will start developing VS2005 rules then. Will it be possible to port the rules to the new version, manual or otherwise Or is this to early to tell

    And thanks again for your help!

    Greetings

  • Judas

    Do you have a time frame for us as to when to expect that "milestone", in other words is it worth to wait for it or will it be a long way out (This ofcourse apply's to some custom development now or later )

    Greetings

  • MP2006

    If you are using VS2005, there's no reason you couldn't start to develop custom rules. The rule API here won't change for a significant amount of time.

    The standalone tool will change, however, and this work will migrate to VS in a future version down the road.

  • DeadlySpider

    We always attempt to provide guidance on porting. Most changes in the past have been very straightforward, as we've modified interfaces or changed the XML standard. It might be trickier in the future, as we will possibly move to a different metadata abstraction. The more exotic the rule code, the more likely a problem in the future. Examining a Method.Body is likely to result in a painful port in the future (depending on the analysis that's being done).

    We'll do everything we can to ease the pain, of course. 8)

  • Rachel Falzone - MSFT

    The VS2005 Team System Developer SKU contains a version of FxCop that's nearly identical to the standalone version available on www.gotdotnet.com. The most obvious difference is that the spelling rules do not appear in VS2005, due to problems getting this functionality working across all supported VS languages. We will address this in the next VS update.

    Custom rules development in VS2005 is an officially unsupported experience (though we did so some sanity testing to make sure it was, in fact, possible to get custom rules working). The rules SDK does not differ from FxCop 1.32. We're about to start a development milestone, however, that wil change several areas of the API. These differences will appear in the free version of FxCop before they show up in VS2005.



  • New Version of FxCop
Answer this question