You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just create a new windows forms project under VS2015 and add the StyleCop.Analyzers analyzer.
Resolve all warnings in the IDE by adaption of the code - but do not activate the documentation build.
If you now build the project you will face a additional warning like the following in the build output:
1>C:\temp\TestStyleCopAnalyzers\TestStyleCopAnalyzers\Form1.cs(14,24,14,29): warning SA1601: Partial elements must be documented
Also it seems that the missing documentation build raises a lot of other false positives.
If this is a know behavior please close this issue immediately - and maybe add this fact to the documentation more prominent.
The text was updated successfully, but these errors were encountered:
alaendle
changed the title
False positive of SA1601 on windows forms.
False positive of SA1601 on windows forms - if documentation build XML isn't eanbled.
Aug 12, 2015
In cases where XML documentation output is disabled, the only reported diagnostic for documentation comments should be SA1652 (EnableXmlDocumentationOutput). Many analyzers which examine documentation comments naturally do not run when documentation output is disabled (because they look at comments that already exist). We only need to update the others to handle this case specifically.
I believe the only one I updated already was SA1600.
Just create a new windows forms project under VS2015 and add the StyleCop.Analyzers analyzer.
Resolve all warnings in the IDE by adaption of the code - but do not activate the documentation build.
If you now build the project you will face a additional warning like the following in the build output:
1>C:\temp\TestStyleCopAnalyzers\TestStyleCopAnalyzers\Form1.cs(14,24,14,29): warning SA1601: Partial elements must be documented
Also it seems that the missing documentation build raises a lot of other false positives.
If this is a know behavior please close this issue immediately - and maybe add this fact to the documentation more prominent.
The text was updated successfully, but these errors were encountered: