![]() The main point of checking is to make sure that problems detected by the analyzer do not make it into the master branch when merging. ![]() The difference will be in getting a list of files for analysis and will depend on which systems you are using. If you are interested in configuring checks of commits or pull requests, you can also do this using this mode. It looks like this: pvs-studio-dotnet -t path/to/solution.sln -f fileList.txt -o project.json To check certain files, specify the -sourceFiles ( -f) flag and pass. But since this is not very convenient, we have added the ability to pass. ![]() xml to the analyzer with a list of files. Previously, in order to check certain files, one had to pass. Can analyze the code meant for 32-bit, 64-bit and embedded ARM platforms.īy the way, we've released PVS-Studio 7.08, which was full of new sapid features. Works in 64-bit systems on Windows, Linux and macOS. PVS-Studio is a tool designed to detect errors and potential vulnerabilities in the source code of programs, written in C, C++, C#, and Java. Enjoy the reading and have a nice unicorn mood. Today we will tell you how to configure the PVS-Studio C# analyzer for checking merge requests. Do you like GitLab and don't like bugs? Do you want to improve the quality of your source code? Then you've come to the right place.
0 Comments
Leave a Reply. |