Out-of-the-box, SonarLint reports issues on the files you're editing.
There are a few more options you can use if you wish.
After install, a startup notification will ask for installing support for additional languages. You can also do it anytime in the Visual Studio Options, under the SonarLint menu item. Issues in these languages are detected whenever you save files.
If Visual Studio full solution analysis is enabled (see here) you can trigger an analysis under the usual Visual Studio Analyze menu, and SonarLint will report all issues it finds.
SonarLint is integrated with Microsoft Code Analysis framework, rules can therefore be fine-tuned in the .ruleset file used by your project.
In the Output panel, show output from SonarLint. Verbosity can be increased in the VS Options, under the SonarLint menu item.
To have rules, issues and exclusions synched. First connect to a server via Manage SonarQube Connections (under Analyze menu). Then, in the Team Explorer SonarQube view, search and bind to a project. If the server-side config changes, you will be notified to Update your local config. Connected Mode only applies for C# and VB.Net code.
Improve software quality and get the most value - find out how you can go further as a team with Connected Mode.
Visit our issue tracker, fork SonarLint on GitHub and submit pull requests.
38 new VB.NET rules analyzed in SonarLint for Visual Studio v4.6
Get in touch and share feedback on SonarSource Community Forums.
