But we already encountered two problems at once that could bring more trouble later. It didn't take us much effort to port the plugin to Visual Studio 2019 and have it launch and run well. Did the new approach help us in support of Visual Studio 2019? Read on to find out. This hope already started to prove realistic as the numerous updates of Visual Studio 2017 were released. Tackling those problems ultimately led up to significant changes to the analyzer, and we were hoping that the new approaches applied then would help us support future versions of Visual Studio/MSBuild much easier and faster. Knowing these details may help you to better understand the current article. That article discusses the issues that we faced last time and the model of interaction between different components (such as PVS-Studio, MSBuild, and Roslyn). In addition to huge changes to many of the IDE's API extensions, we also encountered a problem with maintaining backward compatibility of the new C# analyzer added shortly before that (as well as of the new analyzer layer for C++ to work with MSBuild projects) with the new versions of MSBuild/Visual Studio.Ĭonsidering all of this, I strongly recommend that you see a related article about support of Visual Studio 2017, " Support of Visual Studio 2017 and Roslyn 2.0 in PVS-Studio: sometimes it's not that easy to use ready-made solutions as it may seem", before reading on. Things changed when Visual Studio 2017 released.
![visual studio 2019 requirements visual studio 2019 requirements](https://i0.wp.com/warecrack.com/wp-content/uploads/2019/03/Visual-Studio-2019-Crack-With-Serial-Key-Free-Download.jpg)
Besides, PVS-Studio had only one analyzer back then - for C/C++. Every now and then we would have to add support for new features of C++, which the Visual C++ compiler was gradually learning to work with, but it generally wasn't a difficult task either and could be easily done right before a new Visual Studio release.
![visual studio 2019 requirements visual studio 2019 requirements](https://lowleveldesign.files.wordpress.com/2020/12/aspnet-docker-profile.png)
Since the first version of PVS-Studio that shipped with a plugin for Visual Studio (it was Visual Studio 2005 back then), supporting new versions of this IDE has been quite a trivial task for us, which basically came down to updating the plugin's project file and dependencies of Visual Studio's various API extensions. In this article, I will explain what problems we encountered when implementing support of the IDE and how we addressed them.īefore we start, I'd like to take a look back at the history of supporting the previous versions of Visual Studio in PVS-Studio so you better understand our vision of the task and solutions that we came up with in every single situation. Support of Visual Studio 2019 in PVS-Studio affected a number of components: the plugin itself, the command-line analyzer, the cores of the C++ and C# analyzers, and a few utilities.