What's New in the Intel C++ Compiler integration with Microsoft* Visual Studio*
New in Intel(R) C++ Composer XE 2013 Integration in Microsoft* Visual Studio*
Support Visual Studio 2012* (requires Professional edition or above for IDE integration)
New feature "Performance Guide" under menu [Tools > Intel Composer XE 2013 > Start Performance Guide]
this feature requires Intel VTune Amplifier XE
it is available within Visual Studio 2008, 2010 and 2012
New UI for PGO and Code Coverage
New UI for Intel Static Analysis
Support of separate Intel IPP threaded static library package
Performance libraries and Intel compiler redist paths are passed to Intel C++ and VC++ projects
Added two new macros: ICRedistPaths and VCRedistPaths
New in Intel C++ Compiler 12.0 or 12.1 Integration in Microsoft* Visual Studio*
Support Visual Studio 2010* (requires Standard edition or above for IDE integration)
Support msbuild when using with Visual Studio 2010*
No similar toolbar like in Visual Studio 2010. Those functionalities are provided from "Project" menu or project "Context" menu
Support "Guided Auto Parallelism" analysis on project, file, and code block levels
Support one click Intel Static Analysis in update 6 and newer
New in Intel® C++ Compile 11.1 Integration in Microsoft* Visual Studio*
Intel® Parallel Debugger Extension is added and a new toolbar
Documentation is integrated into Visual Studio IDE
.chm documentation is also available and accessible from Start menu
New project properties for parallel lint options
New project property for using Parallel Debugger Extension
Intel C++ Compiler toolbar enhanced with a new icon to set include & link directories for Intel IPP & Intel TBB -
New in Intel® C++ Compile 11.0 Integration in Microsoft Visual Studio
Support the native Intel® 64 compiler
New project properties for Source Verifer feature under "C/C++->Diagnostics"
New project properties for enabling different level of optimization diagnostics under "C/C++->Diagnostics"
New Profile Guided Optimization menu under "Project"
Support "continue on error" for compilation
Added automation interfaces for manifest tool
New in Intel® C++ Compile 10.1 Integration in Microsoft Visual Studio
Support Visual Studio 2008* from compiler update w_cc_p_10.1.020 or newer
Improved support of the manifest feature
New in Intel® C++ Compiler 10.0 Integration in Microsoft Visual Studio
Visual Studio .NET 2002* is not supported
Support the Inherited Project Property Sheet feature of Visual Studio 2005*
Support the Custom Build Rule feature of Visual Studio 2005
Improved support for remote debugging of Visual Studio 2005
Support the automation interfaces of the Intel C++ Project System
Added a tool bar with three icons in Visual Studio .NET 2003 and Visual Studio 2005. The three icons are: Quick Start Help, Use Intel C++, Use Visual C++
Support the Project Property Sheet feature
The command line tool for project conversion is " ICProjConvert100.exe". It's installed under <common files>intel\\shared files\\ia32
•New project properties for enabling different level of optimization siagnostics under "C/C++->Diagnostics"
Please correct this typo --> siagnostics to diagnostics on our website
We have great difficulties with Microsoft Visual Studio 2008 (VC9), the manifest issues drives us nuts. We are considering to switch to Intel C++ compiler and wondering if there is a manifest trap here as well?
We are currently using STLPort, since MS STL is too slow. Any comments on Intel STL issues?
The sounds of one compiler works for Windows/Linus/Mac OS is really great.
Thank you for your questions.
Regarding the manifest issues. We have our own implementation of the manifest support but it's very close to what MS VC++ does. Please, could you provide more details on what the issues are? It would be great to have some scenario with reproducer so that we could check it with Inel compiler integration.
Comments
•New project properties for enabling different level of optimization siagnostics under "C/C++->Diagnostics"
Please correct this typo --> siagnostics to diagnostics on our website
regards heinz
We have great difficulties with Microsoft Visual Studio 2008 (VC9), the manifest issues drives us nuts. We are considering to switch to Intel C++ compiler and wondering if there is a manifest trap here as well?
We are currently using STLPort, since MS STL is too slow. Any comments on Intel STL issues?
The sounds of one compiler works for Windows/Linus/Mac OS is really great.
Hi,
Thank you for your questions.
Regarding the manifest issues. We have our own implementation of the manifest support but it's very close to what MS VC++ does. Please, could you provide more details on what the issues are? It would be great to have some scenario with reproducer so that we could check it with Inel compiler integration.