I decided to fool around a bit with the plugin and the picture to attract your attention. A whole lot of articles on programming regularly appear on the Internet, but most of them are unfortunately brief and all about nothing. But we are sure that our material is extremely useful, and it will be a pity if it remains unnoticed. We tell our users in every detail about how to develop plugins in C# for the Visual Studio 2005/2008/2010/2012 development environment. This material is based on our own experience and describes some subtleties you won't read anywhere about.
Now let's look closer what I offer you to read.
While developing the PVS-Studio code analyzer, we have acquired an invaluable experience of creating plugins for the Visual Studio environment. This subject is not only complicated but also requires that you know many nuances and subtleties. We believe it'll be useful if we share our knowledge with other programmers so that they will make fewer slips. You will learn how to create plugins after reading the articles. On the picture you can see what I have made out of PVS-Studio. Your own plugin will be much more useful, I suppose.
Our enthusiastic worker Pavel Eremeev has found the time to prepare the necessary article series. So, you are welcome:
I take this opportunity to invite you to join us in Twitter @Code_Analysis or Redding Viva64. There we post links to our own articles and third-party articles on programming. Join us and you won't regret. I try to collect and post really interesting links.
As a PVS-Studio's developer, I am often asked to implement various new diagnostics in our tool. Many of these requests are based on users' experience of working with dynamic code analyzers, for example Valgrind. Unfortunately, it is usually impossible or hardly possible for us to implement such diagnostics. In this article, I'm going to explain briefly why static code analyzers ...