We’re using Sonarcloud for analysis and have bound one of our solutions through the Sonarlint VS2017 extension. I noticed when using Sonarlint, I had no warnings appearing in the Error List for the solution, even when running a full code analysis.
From the Sonarlint output window, I could see that the solution was bound correctly, and was running for all projects apart from test projects, but no warnings were being given.
After spending a bit of time trying to find out what was wrong, in the end, it was solved by opening a file that had a pre-existing warning from the last analysis in Sonarcloud itself, and now warnings are appearing for all files.
It raises the following questions;
Is this intentional? It seems like it wouldn’t be as it isn’t intuitive, or documented.
Are test projects automatically excluded from analysis? Not a bad thing, just want to confirm.
When exactly is the analysis run when opening a solution? Is it only when opening a file that has an issue, as seems to be the case from my experience noted above, or is this an issue?
Since I have opened one file in a solution that contained a pre-existing error, opening other solutions does show the warnings for them even though they are not yet bound to Sonarcloud. Is it intended that Sonarlint can be ran standalone, or bound to Sonarcloud? (Want to make sure there isn’t an issue here either - this isn’t an issue as we’ll be binding all our solutions over time).