SonarLint for Visual Studio v7.8 delivers support for C++23, new rules, and ends support for VS 2019.

• We now support C++23
• Support for VS 2019 ends with this release 
• Support for NodeJS v16 ends as well
• We’ve added two new rules for ASP.net

Discover more with our release notes and community announcement. 

We are deprecating the support of Visual Studio 2019 with SonarLint. 

SonarLint for Visual Studio v7.8 will be the final supported version for Visual Studio 2019 and all efforts will be focused on the 2022 version.

We will maintain SonarLint for Visual Studio 2019 for 6 months. No new features will be implemented.

Learn more with this community announcement.

SonarLint for Visual Studio v7.5 enhances the user experience in connected mode to SonarCloud or SonarQube by allowing you to interact with the status of an issue without leaving your IDE.

Now, you can choose to resolve an issue that you’re not going to fix as Won’t Fix or False Positive. This new issue status will be synced with SonarQube, SonarCloud, and all other contributors using SonarLint in connected mode.

Immediately available for issues already detected by a previous branch analysis in SonarQube or SonarCloud - this will be enabled for new issues in a future release.

Learn more with this community announcement and release notes.

SonarLint for Visual Studio v7.4 enables any contributor to export their connected mode configuration to a file, which can be committed and shared with team members working on the same solution.

Plus:

• Support for .NET 8 and C# 12
• New JavaScript rules

Learn more with this community announcement and release notes.

SonarLint for Visual Studio v7.3 introduces the adoption of Clean Code attributes to categorize issues.

We have made various product changes in alignment with our Clean Code vision. For each issue raised in your code, SonarLint will now report the Clean Code attribute and software qualities impacted.

You can learn more here, in the new SonarLint for Visual Studio documentation.

Plus you can check out the community announcement and release notes.

This release brings enhancements in SonarQube to SonarLint synchronization, code examples, and documentation.

Now any changes in the project Quality Profile configured in SonarQube will be synched in near real-time to the IDE. This means only relevant issues in your code are reported by SonarLint when connected mode is enabled.

In addition, we’ve enhanced our rule descriptions with code diff highlighting between non-compliant/compliant code examples. This is designed to help developers easily understand examples and quickly resolve issues.

And finally, we have enhanced and moved all SonarLint documentation to a central location: https://docs.sonarsource.com/sonarlint/visual-studio/ as part of this initiative.

Learn more with this community announcement and release notes.

This packed release brings a variety of new rules and enhancements!

Firstly, we added new Date & Time rules for .NET. These cover a wide range of topics, and common pitfalls, including time zone conventions, date parsing & formatting, and time arithmetic.

In addition, we’ve added many new MISRA C++ 2023 rules to support mission-critical software environments.

We have also added the ability for SonarLint to detect and report Security Hotspots in local code when used in connected mode to SonarCloud or SonarQube. SonarLint will display any Security Hotspots not yet reviewed as Safe or Fixed. This feature is currently available for C, C++, JavaScript, and TypeScript.

Plus:

• 5 new rules for core JavaScript and TypeScript features
• New rules for C and C++ to detect tricky bugs

Learn more with this community announcement and release notes.

SonarLint for Visual Studio v7.0 brings a modification to the method and location used for storing connected mode settings and data.

Beginning with this version all settings and data will be stored only at this location:

%AppData%\Roaming\SonarLint for Visual Studio\Bindings

SonarLint will automatically propose to migrate the settings, which should take a matter of seconds to complete. A migration guide is also available.

Plus

• New rules to help you avoid performance pitfalls for C# and VB.NET 

Learn more with this community announcement and full release notes.

This release delivers support for CSS analysis.

Designed to help front-end developers write clean code in their Visual Studio IDE we have added CSS to the growing list of supported languages, which includes C#, VB.NET, C, C++, Javascript, and TypeScript. 

A full list of supported rules to detect bugs and code smells in your CSS code can be found here.

Plus:

• New rules for C#, VB.NET, TypeScript

Learn more with this community announcement and full release notes.

This release delivers a new format for the Rule Help feature, plus the ability for SonarLint to retrieve server settings for .NET files.

Now, when clicking on an issue's code in the Error List you will be presented with contextualized guidance as to:

Why this is an issue | How to fix it | More info 

Initially available for the top 15 security vulnerabilities, this feature is being progressively rolled out for all remaining rules, helping developers learn as they code.

Plus, leveraging the power of connected mode to SonarCloud and SonarQube, SonarLint will now retrieve the server settings for .NET files and directories. The following settings are now replicated and applied to your local analysis:

• sonar.inclusions
• sonar.exclusions
• sonar.global.exclusions

Learn more with this community announcement and full release notes.