Missing XML comment for publicly visible type or member(external_roslyn:CS1591)ROSLYN

[Monish_Tyagi]

How to disable this type of rule globally in sonarqube?

[Colin]

Customize Severity or Disable some of roslyn warnings on sonar cloud?

Hi @Leonardo-Ferreira , You can configure Roslyn analyzers in your project using .editorconfig files: Configure code analysis rules - .NET | Microsoft Docs You can also disable importing external Roslyn issues in your SonarCloud project settings under General Settings / External Analyzers / C# section / Ignore issues from external Roslyn analyzers.

[Monish_Tyagi]

I don’t want to ignore all issues from external roslyn analyzers only some issues, i need to ignore .So what changes can i made through UI or in setup to config this .Please help

[Colin]

As Pascal notes in the linked post

@Customize Severity or Disable some of roslyn warnings on sonar cloud?

You can configure Roslyn analyzers in your project using .editorconfig files: Configure code analysis rules - .NET | Microsoft Docs

These changes will be reflected in what issues are raised and uploaded to SonarQube.

[Monish_Tyagi]

Thankyou for reply .
But apart from making changes in .editorconfig file or disable external roslyn analyser through UI. We want to disable some specific rules of rosyln analyzers either from UI side or through modifying some configuration in sonarqube setup project or may be some other approach, as it is our requirement. If there is another approach to do that , please share the information.

[Colin]

@Monish_Tyagi

We want to disable some specific rules of rosyln analyzers either from UI side or through modifying some configuration in sonarqube setup project or may be some other approach,

It’s not possible like this.

[Joe]

Hi @Monish_Tyagi ,

Check out this link that may help:

Roslyn rule excluded by “nowarn” still appearing in Sonar

I wanted to close the loop on this. I wasn’t able to do anything within Sonar, but I was able to pass a parameter to MSBuild --property:GenerateDocumentationFile=false that prevented this particular issue from occurring.