SonarLint on VS 2022 only shows errors in "opened files" regardless of scope choice

SonarQube for IDE Visual Studio
1

Hello
Env details:
OS: Win 10 22H2 19045
Visual Studio version: 2022, 64bit, 17.10.2
SonarLint plugin version: 8.0.0.92083
Programming language : C#
Is connected mode used:No

Problem:
I compile the whole solution successfully and do anylyze => Run code analysis → run on project

Then I go to VS “errors list” and choose “build+intelisense” or just “intelisense”.to see the SL errors.
However it only shows the errors of the opened files even if I choose “Entire solution” from the drop list. If I choose “current project” it shows an empty list. So, when in “Entire solution” mode - the more files I open, the more SL errors are revealed, but there is no way for me to see all errors of project/solution
Appreciate any help on this.
Thanks

2

Hey there.

Analyzing the entire solution should indeed show issues outside of open files.

Can you pull the (preferably verbose) logs when trying to analyze the entire solution?

3

Hi Colin. This is the log
Initializing the daemon package…
[SLCoreHandler] Creating SLCore instance
[SLCoreHandler] Starting SLCore instance
Finished initializing the daemon package.
[SLCORE] Can’t open directory channel. Log directory fsync won’t be performed.
[SharedBindingConfigProvider] SonarLint shared folder was not found
Initializing the SonarLint package…
Finishing initializing the SonarLint package
Initializing the notifications package…
Not connected: not checking for notifications
Finished initializing the notifications package

4

Hey @Zvika

Sorry for coming back to this so late. Can you still reproduce this on v8.1 of SonarLint for Visual Studio?

5

Hi Colin, this still happens on 8.1
btw, tried 8.2 but it gets VS2022 stuck on solution load so had to go back to 8.1
Thanks

6

Also, after installing 8.1 it upgrades automatically to 8.2 and VS is now stuck again. How can I prevent auto upgrade?
Thanks

7

Did v8.2.1 fix this issue?

I believe you turn off automatic upgrades as described here.

8

Mine wont show any SonarLint related erros unless, when lukcy, I can hover a small squiggle on an open document. Then at the very bottom of my VS 2022 Preview status bar, it shows SXXXX … but I would expect it to be part of Warnings list.

9

I was stuck with the same error. It worked for me after setting Java SDK

image
image1066×624 28.8 KB