Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ignore CS1591 in release mode
See original GitHub issuehttps://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs1591
This needs to be added to each project:
<PropertyGroup Condition="'$(Configuration)'=='Release'">
<noWarn>1591</noWarn>
</PropertyGroup>
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How disable “warning CS1591: Missing XML comment for ...
I think some developer was “warning CS1591” when use XML documentation file. I try to find answer and i found it in stackoverflow....
Read more >Compiler Warning CS1591 "Missing XML Comment" isn't ...
I've searched and only found questions from people who want to suppress this warning such as Visual Studio Disabling Missing XML Comment Warning ......
Read more >Disable CS1591 "Missing XML comment" on generated ...
Reporting CS1591 on generated code (i.e. classes marked with GeneratedCodeAttribute) is annoying, since the code may be re-generated at each ...
Read more >Suppress compiler warnings - Visual Studio
In Solution Explorer, choose the project in which you want to suppress warnings. · Right-click on the project node, and choose Properties on...
Read more >Suppress code analysis warnings - .NET
This article covers the various ways you can suppress warnings from code analysis when you build your .NET app. You can suppress code ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The purpose of this is to eliminate >8000 lines of warnings in the Travis CI output, which causes us to have to download the raw log to view it.
Long term we will add it back, but there are so many warnings right now, nobody will be motivated to fix it.
Yes, we can definitely use it manually on just the methods we want. But even that takes a lot of effort, since we have tons of code without XML comments.
The Pro version supports automatically commenting all code in a project. I’ll take a look at the docs if it’s possible to configure to just add comments where it’s missing.