Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29286 Discussions

Integration of IVF 10.1.021 in Visual Studio 2003 failed

markus
Beginner
384 Views
I have a working installation of Visual Studio 2003 and Intel Fortran 9.1. But upgrading to 10.1.021 failed with a message box "Package Intel Fortran Project Package has failed to load properly (GUID = {B68A201D-CB9B-47AF-A52F-7EEC72E217E4}) etc.

I have tried everything, complete uninstall of Intel Fortran, reinstall of Visual Studio, nothing helped.

At last, I have found following:
  • What fails is the part of the installation which integrates IVF with Visual Studio. The compiler itself and idb are ok.
  • The message above comes from Visual Studio. The same message box appears when going to Help -> About in in Visual Studio (after the unsuccessful IVF nstallation)
  • There is a file integrate.bat in the Visual Studio directory (in my case it is "h:ProgrammeMicrosoft Visual Studio .NET 2003Intel FortranVFPackagesintegrate.bat")
  • In integrate.bat there are several regsvr32 calls. I have just played around and obviously it helps to copy the last entry (regsvr32 /s VFHieEditor.dll) to the top of the list. Then you must call integrate.bat with the path to vsvars32.bat as argument (which is also somewhere in the Visual Studio directory). Voila :-)
At the end the compiler integration in Visual Studio works, but I would not call this a stable installation procedure.

Markus

0 Kudos
1 Reply
Steven_L_Intel1
Employee
384 Views
The order of the entries in integrate.bat is deliberate, as some of the DLLs must be registered before others. Unfortunately, if anything goes wrong in the registration, no error message is displayed and the result is that the integration does not work. Sometimes doing the registrations manually, without /s (silent), helps identify the problem, and sometimes it just works to repeat the registrations.

In many cases, we have found customers whose systems have, inexplicably, had portions of the registry "protected" against write by administrators!
0 Kudos
Reply