When Visual Studio is set to generate XML comment files it will print out warnings for each public member that has no comment. Sometimes you want to ignore some of the warnings (say you have a bunch of pretty much self explaining enum entries. Even worse: you have some generator that creates code without comments) What I have seen many times is that someone decides it’s not worth fixing 100 warnings and disables the creation of XML comment files for the whole project. <\/p>\n
You don’t have to do that: Simply use a #Pragma statement to tell the compiler to stop issue warning for a certain Type:<\/p>\n
#pragma warning disable 1591<\/p>\n
When the section finishes and the warnings should be produced again use the following:<\/p>\n
#pragma warning restore 1591<\/p>\n
Of course you can do this with any other warning. The example uses the warning CS1591 (Missing XML comment for publicly visible type or member) but you can apply this to any warning, just ignore the CS prefix.<\/p>\n","protected":false},"excerpt":{"rendered":"
When Visual Studio is set to generate XML comment files it will print out warnings for each public member that has no comment. Sometimes you want to ignore some of the warnings (say you have a bunch of pretty much self explaining enum entries. Even worse: you have some generator that creates code without comments) … Continue reading Ignore missing XML comments<\/span>