Intel C++ and Fortran Compilers for Windows* - Required Microsoft* development software

This article provides an overview of the Microsoft development software required to use the Intel® C++ and Intel® Visual Fortran Compilers as part of Intel® Parallel Studio XE 2017. For more details, refer to the product Release Notes. Abbreviated information on older versions is below.

Microsoft Development Software Requirements

To use the Microsoft Visual Studio* development environment or command-line tools to build IA-32 or Intel® 64 architecture applications, one of:

  • Microsoft Visual Studio 2015* Community Edition or higher with C++ component installed (NOTE! Microsoft Visual Studio 2015 does not install the C++ component by default - you must select it using the Customize option during installation.)
  • Microsoft Visual Studio 2013* Community Edition or higher with C++ component installed
  • Microsoft Visual Studio 2012* Professional Edition or higher with C++ component installed
  • For Fortran only - Intel® Visual Fortran development environment based on Microsoft Visual Studio 2013 Shell (included with Commercial and Academic licenses of Intel® Parallel Studio XE)
    • NOTE! Intel® Visual Fortran development environment based on Microsoft Visual Studio 2013 Shell is included with Academic and Commercial licenses for Intel® Visual Fortran. It is not included with Evaluation or Student licenses. This development environment provides everything necessary to edit, build and debug Fortran applications. Development of C++ applications is not supported by this environment. Some features available with the full Visual Studio product are not included, such as:
      • Resource Editor (see ResEdit*, a third-party tool, for a substitute)
      • Automated conversion of Compaq* Visual Fortran projects

Microsoft Visual Studio Express Editions do not provide full functionality for Intel® compilers and are not recommended.

Intel® Advisor XE, Intel® Inspector XE, Intel® Trace Analyzer and Collector, and Intel® VTune Amplifier XE, included with some editions of Intel® Parallel Studio XE, are supported from the Fortran-only development environment based on Microsoft Visual Studio Shell.

Previous Versions

The following lists Microsoft Visual Studio versions supported by previous versions of the Intel® compilers . Also noted is information on the included Fortran development environment, if any.)

  • Intel® Parallel Studio XE 2016 (compiler 16.0) VS2010, VS2012, VS2013, VS2015 (includes VS2013 Shell)
  • Intel® Parallel Studio XE 2015 Update 4 or later (compiler 15.0.4) VS2010, VS2012, VS2013, VS2015 (includes VS2010 Shell)
  • Intel® Parallel Studio XE 2015 Initial release through update 3 (compiler 15.0) VS2010, VS2012, VS2013 (includes VS2010 Shell)
  • Intel® Composer XE 2013 SP1 Update 1 or later (compiler 14.0.1) - VS2008, VS2010, VS2012, VS2013 (includes VS2010 Shell)
  • Intel® Composer XE 2013 SP1 initial release (compiler 14.0.0) - VS2008, VS2010, VS2012 (includes VS2010 Shell)
  • Intel® Composer XE 2013 (compiler 13.0 and 13.1) - VS2008, VS2010, VS2012 (includes VS2010 Shell)
  • Intel® Composer XE 2011 (compiler 12.0 and 12.1) - VS2005, VS2008, VS2010 (includes VS2008 Shell (12.0) or VS2010 Shell (12.1))
  • Intel® C++ and Fortran Compilers 11.1 - VS2005, VS2008 (includes VS2008 Shell)
  • Intel® C++ and Fortran Compilers 11.0 - VS2003, VS2005, VS2008 (includes VS2005 Premier Partner Edition)
  • Intel® C++ and Fortran Compilers 10.1 - VS2003, VS2005, VS2008 (includes VS2005 Premier Partner Edition)
  • Intel® C++ and Fortran Compilers 10.0 - VS2003, VS2005 (includes VS2005 Premier Partner Edition)
  • Intel® C++ and Fortran Compilers 9.1 - VS2002, VS2003, VS2005 (requires separate Visual Studio)
  • Intel® C++ and Fortran Compilers 9.0 - VS2002, VS2003 (requires separate Visual Studio)
  • Intel® C++ and Fortran Compilers 8.1 - VS2002, VS2003 (requires separate Visual Studio)
  • Intel® C++ and Fortran Compilers 8.0 - VS2002, VS2003 (requires separate Visual Studio)
For more complete information about compiler optimizations, see our Optimization Notice.