FxCop not exclude issues in Designer files

[api...@excentia.es]

Hi, 

I have problems with FxCop, because it is detecting issues in autogenerated code (Designer files) even though I exclude that code with the property sonar.exclusions. Moreover, I also seen in the log that FxCop is executed with /ignoregeneratedcode parameter but it seems that not exclude that code.

Could you help me to exclude that issues?

Regards

[Freddy Mallet]

Hello,

Which version of the C# plugin are you using because in 5.2 we fixed some stuff relating to issue suppression mechanism: https://jira.sonarsource.com/browse/SONARCS-593 ?

Thanks

Freddy

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/6aa68ce3-cd3b-45c2-8579-4371ac6aca30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Freddy MALLET | SonarSource

Product Director & Co-Founder
http://sonarsource.com

[api...@excentia.es]

Hi Freddy, 

We use SQ 5.3, C# 5.2, VB.Net 2.4. I compile with MSBuild 14 and FxCop 14

Regards

[Anantha Madhava]

Hello Freddy,

Even we are facing the same issue. On SonarQube 5.6, C# plugin V5.3.1, the FxCop rules are not considering the sonar.exclusions.
Where as the same pattern for sonar.exclusions are being considered for C# rules other than FxCop rules.

I think this is because of the 'assembly level' violations that are caught by FxCop rules [the violations for which the exact line number is not pointed].

Please suggest how to get this working.

Cheers,
Anantha

[G. Ann Campbell]

Hi Anantha,

Please don't excavate old threads. Open a new one instead.

Ann