CODEWITHSUNDEEP
visual-studiovisual-studio-2017
Mithgroth
Mithgroth

Reputation: 1212

Suppressing warnings for solution

I can't seem to be able to suppress warnings in my solution in Visual Studio 2017 by going into Project Settings > Build > Suppress warnings:

enter image description here

Even when I clean - build, rebuild, etc... the solution, Visual Studio keeps bringing up these warnings for me.

I brought this up with a visualstudio.com report yesterday and it's "triaged" at the moment. Is there an alternative way to suppress warnings in the solution, without marking every single reference?

Version: 15.6.2

Update: This is wierd. Visual Studio 2017 uses a semicolon by default, but comma worked.

Upvotes: 21

Views: 33915

Answers (4)

Amani Mohamed Babiker Eisa
Amani Mohamed Babiker Eisa

Reputation: 1

From project properties you can disable it . Please check the image below enter image description here

Upvotes: 0

BugEyed
BugEyed

Reputation: 21

You may just need to restart Visual Studio. This worked for me, and FYI we do not need to include the CS part of the error in your textbox (it would still work as written though, but you only need the number for this.) You have certainly restarted VS in the years since first asking the question, but for anyone having this problem today, I hope this helps. I had the same issue with the same warning (CS1591). So for "Suppress warnings" in the properties to actually work (rather than the #pragma solution which is a legitimate work-around but might be unnecessary keyboard time after a restart) you might just need to restart Visual Studio.

Upvotes: 1

DhyMik
DhyMik

Reputation: 373

The way I do it solution-wide is to create a specific suppression file, for instance GlobalSuppressionsForTestProjects.cs, in a convenient solution-level location.

Then for each project of the solution where I want the suppression definitions applied, I add a link to the suppression file:

  • right-click on project -> Add -> Existing Item
  • in selection dialog, navigate to the suppression file
  • click on Add as Link

Add existing item as link

I learned this trick from this post where the same way was applied for AssemblyInfo.cs files.

Upvotes: 9

Francesco B.
Francesco B.

Reputation: 3097

I usually use pragma directives:

#pragma warning disable 1591 
// whatever member is lacking xml comments, or even the whole file
#pragma warning restore 1591

Verbatim from the link above:

disable: Do not issue the specified warning message(s).

If you really want to disable warnings solution-wide, there's no way to do it.

All compilation options are specified on the project level. MSBuild exists below the level of solutions.

But it can be done project-wise, just like you were doing above; the only thing I would change is separating those codes using a comma and not a semicolon like in your picture (and without a comma in the end), e.g.:

1591,1701,1702,1705

That's because compiler options use a comma.

Upvotes: 12

Related Questions