Multiple versions of Fortran Compiler and VB Studio 2008?

[esanford]

Can the version 10 compiler and the version 9(or 8) compiler be installed side by side and both intergrate with an install of Visual Studio 2008?

[Kevin_D_Intel]

Yes. The Intel Visual Fortran integrations with Visual Studio 2008 (available with IVF 10.1.019 or later) support having IVF 9.1 and 10.1 installed side-by-side and using either the 9.1 or 10.1 compiler under the IDE.

Under the IDE, you select which compiler is used via:

Tools > Options > Intel Fortran > Compilers > Selected Compiler

You may not use any compilers earlier than IVF 9.1 with Visual Studio 2008.

I recommend you install the IVF 9.1 compiler first using a custom installation and only install the compiler, and then install the complete IVF 10.1 compiler package.

[TimP]

I think there is a confusion here between VS2005 and 2008. For integration with VS2008, a recent ifort 10.1 is required. VS2005 would work as Kevin said. VC installation is required prior to installing ifort; VB installation or removal won't affect ifort.

[Kevin_D_Intel]

Support for integration with VS2008 was first provided in the 10.1.019 update. As long as you install 10.1.019 or any later 10.1 update the integrations with Visual Studio 2008 support using the 9.1 and 10.1 compilers as I described.

We should also make certain we are clear that IVF requires Visual Studio and not Visual Basic. Please refer to the System requirements here

[Steve_Nuchia]

Another caveat: you only get one flavor of Visual Studio integration, regardless of which compilers are installed. It can get tricky when you want to manage compiler flags that changed from one version to another, and you get the bugs for the integration version installed and not the compiler selected.

Also, you can get into trouble if you've got C++ code trying to link with your fortran, changing the compiler selection does not automatically switch what C++ links to. Ditto if you're building an installer (or zip, or whatever) with ifort DLLs in it; your script won't automatically adapt unless you've taken pains to make it do so.

[esanford]

Leaving VS2008 in place, I uninstalled the 9.1, 10, and 11(beta) compilers, and then installed first 9.1 and then the 11 beta. I am only able to see 11 as an option in VS2008 under Tools > Options >Intel Fortran > Compilers. Suggestions as to how to get 9.1 to integrate alongside 11?

[Steven_L_Intel1]

9.1 doesn't support VS2008. If you have VS2005 also installed, you should see 9.1 show up there.

[Kevin_L_6]

(per Steve Nuchia's caveat on a single flavor of vs integration)
My problem is our production codes use ivf9.0 integrated with vs2003; I downloaded vs2008 and ivf11.0 & did that integration (ok), but vs2003 lost connection with ivf90.
I therefore uninstalled all studio and ivf packages, then installed ivf9.0 integrated -i hoped- with vs2003.
it didn't work, so i downloaded and ran repairvs03integration.exe and got this responce:

"Visual Studio .NET 2003 installed at C:Program Files (x86)Microsoft Visual Studio .NET 2003
Error while loading C:Program Files (x86)Microsoft Visual Studio .NET 2003Intel Fortran
VFPackagesVFHieEditor.dll: The specified module could not be found."

... by golly, good catch...
C:Program Files (x86)Microsoft Visual Studio .NET 2003Intel FortranVFPackages>dir
02/17/2009 04:18 PM .
02/17/2009 04:18 PM ..
02/17/2009 04:08 PM 1033
11/04/2008 12:03 PM 77,824 VFAVWin.dll
11/04/2008 12:04 PM 221,184 VFFortSvc.DLL
11/04/2008 12:05 PM 1,478,656 VFProj.dll
11/04/2008 12:04 PM 479,232 VFProjConvert.dll
11/04/2008 12:04 PM 143,360 VFToolOpt.dll
5 File(s) 2,400,256 bytes

..but what's to be done to get our code building again?

[Steven_L_Intel1]

The repair program does not support 9.1 - that DLL is 10.0 and later only.

Here's how to do it manually. Start > Microsoft Visual Studio .NET 2003 > Visual Studio .NET 2003 Tools > Visual Studio .NET 2003 Command Prompt. Set default to C:Program FilesMicrosoft Visual Studio .NET 2003Intel FortranVFPackages Type the following commands:

regsvr32 /u VFAVwin.dll
regsvr32 /u VFFortSvc.dll
regsvr32 /u VFProjConvert.dll
regsvr32 /u VFProj.dll
regsvr32 /u VFToolOpt.dll
regsvr32 VFToolOpt.dll
regsvr32 VFProj.dll
regsvr32 VFProjConvert.dll
regsvr32 VFFortSvc.dll
regsvr32 VFAVwin.dll
devenv /setup

This last command may take a minute or two to execute. The regsvr32 commands should each display a message about success or failure. If any of the /u commands fail, just keep going. If Windows complains that regsvr32 is not defined, start with this command:

set PATH=%SYSTEMROOT%system32;%PATH%

and then do the regsvr32 commands.

[Kevin_L_6]

'Start > Microsoft Visual Studio .NET 2003' pops up devstudio, and there's no 'Visual Studio .NET 2003 Tools'
(maybe it's that i have ivf9.0 -not 9.1-)...

so i cd'd to prog**2003intel* in a dosbox & typed '..common7toolsvsvars32'. the regvr32 commands worked (in the vfpackages folder) for all but *convert.dll (loadlibrary failed). i rebooted & launched vs2003, but 'menu>tools>options>Intel Visual Fortran>compilers>selected complier' displays 'No Compiler installed'

[Steven_L_Intel1]

It sounds as if VS2003 is not properly or completely installed. The lack of the Tools submenu suggests that - it isn't an IVF thing.

You can try these commands from a Fortran Build Environment prompt if you have it set to use VS.NET 2003 for command-line integration.

[Kevin_L_6]

guess i wasn't on the same page: if i hit the startbutton & click 'all programs' i can drill down to studio & select the 'visu*2003 Tools' then 1 more level gives me the prompt (my mistake was in assuming you meant the studio app).

i did repair vs2003 through control panel's "add/remove programs", then used the specified route to invoke a dosbox (with the pre-set environment for using Microsoft Visual Studio .NET 2003 tools). i cd'd to the vfpackages folder, did the 'regserv32 /u' for each dll (in order) then the same command without the '/u' (dlls in reverse order). recieved the same error for vfProjConvert as before, but pressed on. 'devenv /setup' took less than a second, and when the prompt became available, i typed 'devenv'.

vs2003 instanced; t+o produced the Options dialog, but selecting 'intel*'/compilers still shows 'no compiler installed'.

could you be more descriptive of what you mean by 'try .. a fortran build environment prompt'?
thanks for you patience -kevin

[Steven_L_Intel1]

Try the commands I gave you again - using the VS2003 command prompt (since you found it, ignore my suggestion of a Build Environment window - which you could find under Intel Software Development Tools > Intel Fortran Compiler.

Before typing the regsvr commands, type these too:

SET PATH=%SystemRoot%Win32
SET INCLUDE=
SET LIB=

[Kevin_L_6]

I set the environmental variables as directed from (the VFPackages folder within) the 2003 command prompt, but since the system couldn't find %SystemRoot%Win32, i set PATH=%SystemRootsystem32;%PATH% ...then did the regsvr32 commands (same results as before). The 'devenv /setup' command failed (owing to path redefinition). Typing '....common7idedevenv /setup' took about 4 seconds before the command prompt became once again available.

A reboot then "devenv > menu > tools > options > intel*fortran > compilers" still shows "No Compiler Installed", yet >set i
IFORT_COMPILER90=C:Program Files (x86)IntelCompilerFortran9.0
INTEL_LICENSE_FILE=C:Program Files (x86)Common FilesIntelLicenses

What do you think is going on?
Thanks for your continued help -kevin

[Steven_L_Intel1]

Sorry, I did mean System32 and not Win32. I notice that you're doing this on an x64 system - I'm not sure how well VS2003 works in this environment and there might be some issue related to the registry redirection that Windows does for 32-bit apps. Do you really need to use VS2003 there?

[Kevin_L_6]

Quoting - Steve Lionel (Intel)

Sorry, I did mean System32 and not Win32. I notice that you're doing this on an x64 system - I'm not sure how well VS2003 works in this environment and there might be some issue related to the registry redirection that Windows does for 32-bit apps. Do you really need to use VS2003 there?

good point! vs2003 may be assuming the 32bit registry & filesys while my environment's biased toward 64bit configurations - and maybe the 64bit side isn't completely self consistant.

As far as vs2003's necessity: we've invested heavily in validating output from our 23 bit code compiled with ivf9.0/sv2003 agreed with the output from our apps compiled in 16bits. In moving to 64 bits, we need the same kind of assurence (a great deal of pre & post processing is done outside of fortran).

And until we have the validation done, we must continue to build in 32bits.

[Steven_L_Intel1]

While I suppose it's a possibility, I would be skeptical that the 32/64 nature of the registry is to blame here. I just thought I'd throw it out there.

Are you willing to allow me to look at your system through an online interactive session? If so, send me an email at steve.lionel at intel.com and we'll set something up. Let me know what timezone you're in and a range of good times over the next few days. I've been 100% successful at resolving these integration issues with such sessions.

[Steven_L_Intel1]

The problem in this case was that the version 11 integration had been installed and uninstalled, but the uninstall did not actually remove the 11 integration. This blocked the 9.0 integration from installing completely. The 11.0 integration does not support the 9.0 compiler.

The fix was:

1. Manually unregister the integration DLLs
2. Delete the Intel Fortran subfolder under Visual Studio .NET 2003
3. Uninstall the 9.0 integration (which was "installed" but not active)
4. Reinstall the 9.0 integration.