Hello.
I have the same. I see 0 issues in Editor, but 2 issues in the server.
I can see on the log correct number of rules (* cs: 363 active rules) but somehow I’m not getting this in IDE.
This particular rule S1192 is also listed on log as Active.
Even if I call “Analyze All Project files” I’m getting zero issues in IDE.
I found one issue in Logs right after Rider starts… a java exception that mono was not found.
I fixed that by specifying “sonar.cs.internal.monoExeLocation” and this solved a loading error.
But still see 0 issues when trying to analyze files.
Hello @ganncamp
I’m using JetBrains Rider 2025.1.2 on macOS on Apple Silicon device.
I’m using SonarQube for IDE plugin version 10.24.0.81420
On server side: “Data Center Edition - v2025.1.1 (104738)”
After correcting mono path as described above (actually path to: “/Library/Frameworks/Mono.framework/Versions/6.12.0/bin/mono-sgen64” and not “/Library/Frameworks/Mono.framework/Versions/Current/Commands/mono”) it started to work, but I still cannot see the same number.
In example file, I can see on webpage 5 issues, but in IDE only 3. More info on the screenshot. Do I correctly expect to see the same entries in both places?
Thanks for the details and the screenshots. It’s all very helpful.
It seems that we’re missing two issues from the same rule. Could you help me out by clicking though on the server on one of those IDE-missing issues and give me the rule ID please? It will be toward the top-left and should start with csharpsquid.
Hello @ganncamp
The missing one is: csharpsquid:S3267
Now… when I looked at Log again, I think I again can see different value in terms of number of active rules.
Should those number mach? Or maybe it is something connected to my project settings?
Hi,
how can I get the log correctly? Do you mean just copying output on the Log tab?
Should I turn on “Analysis logs”? Should I turn on “Verbose output”?
The point here is that after Rider starts and just analyze one opened one file, the log it too long and begining gets truncated? Can I find log file somewhere on disk?