I suggest you ...

Update standalone FxCop to support .NET 4.5 and Portable Libraries

Please update the standalone version of FxCop to be on par with the latest edition of the Code Analysis in VS 2012 to support developers using the Professional Edition SKU. This implies support for .NET 4.5 and for Portable Libraries.

584 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Carel LotzCarel Lotz shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    11 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Larry GoldingLarry Golding commented  ·   ·  Flag as inappropriate

        Agreed, our build process incorporates the command line FxCop tool and we want to move to Dev 11.

      • MJ MillerMJ Miller commented  ·   ·  Flag as inappropriate

        Just adding my 2c worth. Build machines should have fxcop, express users should have fxcop. Simple.

      • RaffaeuRaffaeu commented  ·   ·  Flag as inappropriate

        Please, our entire ALM process runs around FxCop and it would be really nice to have full integration also with VS2012

      • KaliyappanKaliyappan commented  ·   ·  Flag as inappropriate

        We are using fxCop on a Jenkins and within our build. so it is for us important to get an external tool.

      • Anonymous commented  ·   ·  Flag as inappropriate

        We are using fxCop on a Jenkins and within our nant build tools. so it is for us important to get an external tool.

      • KenKen commented  ·   ·  Flag as inappropriate

        Yes, this would be advantageous to externalize the API as well, and link the embedded with an external interface as the VS UI is getting a little too busy.

      Feedback and Knowledge Base