14

I'm toying with getting our team and projects ready for VS 2019. Right away, trying to set up Code Analysis for a new project, I find this:

enter image description here

So, if this is deprecated (and apparently can't even be used, so I'm thinking "deprecated" really means "gone"), where are we supposed to set up our Rule Sets? Is there some other location, or perhaps an altogether new solution to the problem of style and code quality?

bubbleking
  • 3,329
  • 3
  • 29
  • 49

2 Answers2

12

Going forward, static analysis will be provided by Roslyn analyzers: https://github.com/dotnet/roslyn-analyzers

Migrate from FxCop code analysis to .NET compiler platform analyzers

ardila
  • 1,277
  • 1
  • 13
  • 24
Paulo Morgado
  • 14,111
  • 3
  • 31
  • 59
  • 1
    And here is a section on code analyzers in VS 2019 https://learn.microsoft.com/sv-se/visualstudio/code-quality/fxcop-analyzers?view=vs-2019 – MunchyYDL Apr 10 '19 at 19:17
  • Thanks, @MunchyYDL. I've added that link to the answer. – Paulo Morgado Apr 10 '19 at 19:23
  • I suppose this means I need to dig in more. I was previously under the impression that those Code Analysis rule sets WERE Roslyn analyzers. – bubbleking Apr 10 '19 at 22:05
  • There is a plugin: https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2019 – rasputino Aug 08 '19 at 12:18
  • > If you are already using the equivalent NuGet package (Microsoft.CodeAnalysis.FXCopAnalyzers), then installing this extension will cause issues (see issue here). Please install the latest NuGet package rather than the extension if this is the case. – Paulo Morgado Aug 08 '19 at 14:19
  • You need to install Microsoft.CodeAnalysis.NetAnalyzers (Microsoft.CodeAnalysis.FxCopAnalyzers is deprecated) – Luca Ziegler Dec 09 '20 at 11:02
-3

Microsoft IntelliCode looks great!

Michael Dzuba
  • 123
  • 1
  • 3