CODEWITHSUNDEEP
visual-studioroslynroslyn-code-analysis
Caner Ozden
Caner Ozden

Reputation: 135

Suppressing issues from Roslyn code Analyzers

Is there any way to suppress the issues from the Roslyn Analyzers? I use the instant analyzer project type. And I want to suppress the issues if the user wants it. Also it must be permanent. If I reopen Visual Studio, the same suppression rules must still be applied.

Upvotes: 10

Views: 7739

Answers (3)

Andrew
Andrew

Reputation: 1

Attribute suppressions can also be placed in the GlobalSuppressions.cs file for the project

Upvotes: 0

Maxim
Maxim

Reputation: 13468

In Visual Studio 2017 you can disable Roslyn warnings (like IDE0002, IDE0003, etc.) in project properties:

Screenshot

You can directly edit csproj file if neccessary:

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <NoWarn>IDE0002;1701;1702;1705</NoWarn>
  </PropertyGroup>

As you can see you need to write it with IDE prefix (exactly as it is reported by Roslyn). You have to do that for each build configuration (or create new group without Condition). I think it is fastest and most clear way to disable it for whole project.

Pragma works a bit different most likely due to a bug in VS (so I guess it can be changed later).
For example #pragma warning disable IDE0002 will not show Roslyn messages but it will still highlight code (more grayed).

Upvotes: 9

Jon Skeet
Jon Skeet

Reputation: 1503090

You can ignore warnings/errors from Roslyn analyzers in exactly the same ways as ignoring normal C# compiler warnings:

Upvotes: 10

Related Questions