Problems installed IVF 11 with IVF 10

[martymike]

We are building the current version of our software with IVF 10.1 and Visual Studio 2008. We built the previous version with IVF 9.1 and Visual Studio 2005. Both versions have contining support and releases, i.e. as a developer I am not only working on the next release, but, from time-to-time, researching issues and developing updates for the previous two versions. I therefore have both versions of Visual Studio and both versions of IVF installed, and use both regularly.

We are considering using the current releases of both products for our next software release, IVF 11.1 with Visual Studio 2010. I recently downloaded a copy of Visual Studio 2010, and I started to install IVF 11.1, and I got this message:
----------------------------

Intel Visual Fortran Compiler Professional Edition for Windows* installation can continue, but take note

Intel Visual Fortran Compiler 10.1 Integration(s) in Microsoft Visual Studio* is already installed.

If you proceed to install the IDE integration for Intel Visual Fortran Compiler Professional Edition for Windows* 11.1, the 10.1 IDE integration(s) will co-exist with the new 11.1 IDE integration(s); however, you will be unable to use the Intel Visual Fortran Compiler 10.0 or 9.1 within the Visual Studio IDE (if it is currently installed).
---------------------------
This is alarming because I need to be able to continue to build and debug in any of these combinations at any time. I haven't responded to this message. What should I do?
(btw I'm leaving this message as I'm leaving the office today)

[pbkenned1]

Intel Visual Fortran v11.1 is not supported with Microsoft Visual Studio 2010. Support will be available in the next major version of IVF.

The IDE integration warning messages are correct. Starting with IVF v10.0, every IDE version supports the current and two previous versions of the compiler. So for example, the IVF v11.1 IDE integration supports the 11.1, 11.0, and 10.1 compilers in Visual Studio. For additional details, see this article.

Patrick Kennedy
Intel Developer Support