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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.

>
>
Description of the error of integrating…

Description of the error of integrating Intel Parallel Studio Service Pack 1 into Visual Studio 2005/2008

Feb 13 2010

We noticed an error of integrating Intel Parallel Studio Service Pack 1 into Visual Studio 2005/2008 and would like to describe it in this post and tell you how to fix it. We pursue several goals. First, we hope that Intel Parallel Studio developers will notice this error and fix it. Second, it may help those who use Intel Parallel Studio eliminate this or similar errors if any. Third, this error leads to an incorrect behavior of the analyzer PVS-Studio that we develop and that also integrates into Visual Studio environment.

First, let us take a look at the Visual Studio automation command to show the options window (see Figure 1).

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image1.png

The automation command can be called through a special API provided by Visual Studio for plug-in modules. You may also call various commands using the window "Command Window". You may open it through "View->Other Windows->Command Window" as shown in Figure 2.

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image2.png

If you write the command "Tools.Options" (see Figure 3) in "Command Window", the options window will appear that was shown in Figure 1.

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image3.png

There is one more point to consider. You may assign hot key combinations to commands through the "Keyboard" tab in the settings as shown in Figure 4.

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image4.png

If we input the line "Tools.Options", we will see only one same line in the list (see Figure 5). It is expected and right. Keep this thing in mind.

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image5.png

Now we will install Intel Parallel Studio. Below is the information generated by Intel Parallel Studio during the installation process:

Intel Parallel Studio Service Pack 1
Destination Folder(s)
    C:\Program Files (x86)\Intel\Parallel Studio\Composer\
    C:\Program Files (x86)\Intel\Parallel Studio\Inspector\
    C:\Program Files (x86)\Intel\Parallel Studio\Amplifier\
Components
    Intel Parallel Composer Update 3
        Intel C++ Compiler
            Intel C++ Compiler for applications running on IA-32
            Intel C++ Compiler for applications running on Intel(R) 64
            Integration(s) in Microsoft Visual Studio
            Intel Parallel Debugger Extension
            Integrated Documentation
        Intel Integrated Performance Primitives
            Intel IPP for applications running on IA-32
            Intel IPP for applications running on Intel(R) 64
        Intel Threading Building Blocks
            Intel TBB
    Intel Parallel Inspector Update 2
    Intel Parallel Amplifier Update 2
Configuration Options
    Integration with Microsoft Visual Studio 2005 software
    Integration with Microsoft Visual Studio 2008 software

After installation the command of opening the options window fails. Now, if you input the command "Tools.Options" in "Command Window" (see Figure 6) you will get the message "Command "Tools.Options" is not available.".

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image6.png

A similar problem occurs when trying to use API to open the options window. Here is an example of a call:

Application.ExecuteDTECommand("Tools.Options");

As a result, a failure occurs when addressing this function inside the tool PVS-Studio we are developing (see Figure 7).

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image7.png

We do not know the cause of this error. We can only give you some indirect data. Go back to the settings of the "Keyboard" tab. Now, if you input "Tools.Options", there appear two same lines in the list (see Figure 8).

0056_Description_of_the_error_of_integrating_Intel_Parallel_Studio_Service_Pack_1_into_Visual_Studio_20052008/image8.png

After the reset all the errors disappear and the command of opening the options window behaves as it should.

Popular related articles
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…
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…
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…
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…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
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 Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
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…
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…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 →
Accept