PVS-Studio 7.27: check C# code in VS Code, analyze Unreal Engine projects in Rider, and more

PVS-Studio 7.27 has been released. Now you can analyze .NET projects in the plugin for VS Code, check Unreal Engine projects directly in Rider — and there is more to come! See the details in this note.

Support for .NET projects in the plugin for Visual Studio Code

Now the PVS-Studio plugin for Visual Studio Code supports the analysis of .NET projects. In the plugin, you can:

• run the analysis and view the analysis report;
• suppress warnings using suppress files;
• work with .pvsconfig files;
• and more.

Please see the documentation to learn more about the plugin features.

New features of the Rider plugin

The PVS-Studio plugin is now available for Rider 2023.2. Rider 2023.2 enables you to work with Unreal Engine projects directly in Rider, and with PVS-Studio you can analyze UE projects directly in Rider too! For more details, please see the documentation.

Complete revision of the Java analyzer documentation

Now each usage scenario has a separate section in the documentation:

• Maven integration
• Gradle integration
• Using PVS-Studio in IntelliJ IDEA and Android Studio
• Using the Java analyzer directly from the command line

New feature for pvsconfig

In the pvsconfig configuration file, you can now specify the paths in the analyzer report to be set relative to the solution directory.

The new option is supported both when launching the analysis and when viewing the analyzer results in IDE plugins. The feature will make it easier to handle the analysis report when spreading it between the machines with different directory structures.

You can find the documentation for pvsconfig here.

New diagnostic rules

C++

• V1102. Unreal Engine. Violation of naming conventions may cause Unreal Header Tools to work incorrectly.
• V2623. MISRA. Macro identifiers should be distinct.

C#

• V3192. Type member is used in the 'GetHashCode' method but is missing from the 'Equals' method.
• V4004. Unity Engine. New array object is returned from method and property. Using such member in performance-sensitive context can lead to decreased performance.

Articles

For C++ programmers:

• Oh my C! How they wrote code back in the Quake days
• PVS-Studio vs CodeLite: a battle for the perfect code
• Checking the GCC 13 compiler with the help of PVS-Studio

For C# programmers:

• 5 amusing oddities in the code of Entity Framework Core
• PVS-Studio helps optimize Unity Engine projects

Other:

• Common patterns of typos in programming
• Simple, yet easy-to-miss errors in code

We have also launched an IT events newsletter for developers! Here you can subscribe to the PVS-Studio events and digest newsletter.