Suppressing warnings for solution

Question

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:

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.

Francesco B. · Accepted Answer · 2018-03-30T11:46:00.400

9

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.

edited Mar 30 '18 at 11:46

answered Mar 29 '18 at 20:22

Francesco B.

2,729
4
25
37

MSDN specifies this under C/C++, does this apply to C#? – Mithgroth Mar 29 '18 at 20:25
Yep. Try it and if it works mark my answer as solution :D – Francesco B. Mar 29 '18 at 20:26
3

Sorry, is this placed inline? How can I do this for whole solution? – Mithgroth Mar 29 '18 at 21:04
Whole solution - I don't know. Whole files, yes you can, just put it the first line at the beginning of the file andthe second at the end – Francesco B. Mar 29 '18 at 21:11
1

Unfortunately, that's my real question: A way to deal with this solution-wise. Thanks tho. – Mithgroth Mar 29 '18 at 21:31

score 9 · Answer 2 · answered Mar 06 '20 at 13:09

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

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

score 0 · Answer 3 · answered Aug 27 '20 at 01:53

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.

I wouldnt downvote this. Simply because VS doesn't recognize the change right way if you have those error codes in your error list. But rebuilding has the same effect. It will clear those codes once put in project settings like OP was doing. — michael g, Jul 24 '21 at 06:16

Suppressing warnings for solution

3 Answers3