To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Note about hotkeys

Note about hotkeys

Dec 12 2014

Even if our product, PVS-Studio, position itself as a tool for programmers, and it is the reason why almost all questions sent to tech support are highly specialized (i.e. usually we are not replying something like "Have you tried turning it off and on again?"), sometimes we actually have to reply in Captain Obvious style. One of the questions that is lying in this category is why don't you have a hotkey mapped to check current file / check solution or why hotkeys mapped to "Go to Next Message" and "Go to Previous Message" (Alt+'[' and Alt+']') are chosen to be so inconvenient? OK, let us try to figure out how could have that been happened.


Why these hotkeys?

In general, usually that quickly becomes a nuisance when developing Visual Studio add-ons - proper hotkeys selection. The main idea is that hotkeys is a very convenient tool because it helps to save a lot of time while others slowly move mouse cursor (that is one of the reasons why vi and emacs text editors are so popular). However, there are no use of the hotkey like "Ctrl+Shift+Alt+Numpad 4 while NumLock is off". Neither does the hotkey that requires making multiple chords like Alt+K, Ctrl+L, Ctrl+Shift+Z. Such combinations may make programmer's life more difficult because time spent on pressing those hotkeys is not a lot shorter than time spent on pair of clicks. What was the may reason of hotkeys usage? Nevertheless, there is another problem. Of course, one would like to that jump to next or previous PVS-Studio warning be more accessible, but Visual Studio hotkeys already occupies a large fraction of the keyboard, and the fraction that is not used, are almost certainly taken by the most popular add-ons. This is the reason why we chose the default hotkeys that is not used by Visual Studio nor by the most popular add-ons. However, it is just by default. As you would have probably guessed, every menu option may be mapped (or remapped) to any hotkey.

Hotkey mapping

In this paragraph, we shall explain how to map a hotkey to the "Check current file" item. We shall bind an Alt+'\' hotkey. Of course, similar method can be used to bind hotkey to any item, including "Go to Next Message" and "Go to Previous Message". It should be clear that any hotkey might be bound, not only Alt+'\'.

To do that, first of all one needs to enter "Options" menu of Visual Studio IDE. Screenshots below illustrate all the actions as applied to Microsoft Visual Studio Professional 2012.


Figure 1 - Options menu

After the dialog window pops up, next step is to open "Environment" and choose "Keyboard".


Figure 2 - Keyboard menu

To make search simpler, we recommend entering "PVSStudio" filter into "Show commands containing:" field. This should filter all the possible mapping options to the ones related to PVS-Studio.


Figure 3 - Filtering all the options to ones containing "PVSStudio" keyword.

After that, it is required to locate the required line. In our case it's "PVSStudio.CheckCurrentFile" - Check current file menu option.


Figure 4 - Selecting the "PVSStudio.CheckCurrentFile" line

Next step is to focus the "Press Shortcut Keys" field and press key combination and then click on "Assign" to make binding.


Figure 5 - Mapping "PVSStudio.CheckCurrentFile" to Alt+'\' hotkey

The last step is to press "OK" and make sure everything works as expected.


Figure 6 - Correctly mapped hotkey


Despite the fact that the subject of this note is obvious, we hope that it will be useful to somebody, because it allows not only mapping any hotkey into any command of our tool this way, but also mapping any commands of Visual Studio and commands of other add-ons as well.

Popular related articles
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →