VS 2003 integration

[jgavill]

Hi,
I'm trying to install Visual Fortran 9.1 together with MS Visual Studio .Net 2003 (under Windows XP SP3)

Everythings seems OK :
-The splashscreen when starting VS shows the Fortran logo.
-Help menu contains "Intel Fortran Compiler Help" item.
-Help/"About Microsoft Development Environment" menu shows "Intel Fortran Compiler Integration" in the "Installed Products" list
-File/New/Project menu contains "Intel Fortran Projects"
-Openning an example Fortran file shows that the syntaxic-coloration is working.

But when trying to start run the example program, the debug output log shows following lines :

'console3.exe': Loaded 'C:\\Documents and Settings\\localadmin\\Mes documents\\Visual Studio Projects\\Console3\\Debug\\Console3.exe', Symbols loaded.
'console3.exe': Loaded 'C:\\WINDOWS\\system32\\ntdll.dll', No symbols loaded.
'console3.exe': Loaded 'C:\\WINDOWS\\system32\\kernel32.dll', No symbols loaded.
'console3.exe': Loaded 'C:\\WINDOWS\\system32\\imagehlp.dll', No symbols loaded.
'console3.exe': Loaded 'C:\\WINDOWS\\system32\\msvcrt.dll', No symbols loaded.
The program '[752] Console3.exe: Native' has exited with code 0 (0x0).

I tried repairvs03integration.exe and I get the following error :
"Error while loading C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Intel Fortran\\VFPackages\\VFHieEditor.dll: Can't find the specified module."

I tried several new installations on several computers, but the VFHieEditor.dll is always missing...

I don't know what else to do...

Thank you for your help.

Jol

[anthonyrichards]

It looks like your console program ran to completion and exited OK.
If you need to run in debug mode and stop to look at variables, you have to insert at least one breakpoint
somewhere, which it seems you haven't.

[jgavill]

Thanks for your Reply
First thing : I'm a technician in charge to install softwares oncomputers of my company, I'm not a programmer.
The end user of the computer is a programmer and he report us that the Fortran compiler doesn't work on his machine.
He gave me the following code to makesome tests :

program add
c
c John Mahaffy, Penn State University, CmpSc 201 Example
c 1/26/96
c
c
c This is a simple program to read 2 numbers and print the sum
c
implicit none
real a,b,s
c
c a - one of two numbers to be added
c b - the other number in the sum
c s - the sum of a and b
c
c Get the numbers from the program user
c First ask for the numbers
c
print *, ' This program adds 2 real numbers'
print *, ' Type them in now separated by a comma or space'
c
c Now read the numbers that are typed by the user
c this Fortran read will wait unil the numbers are typed
c
read *, a,b
c
c Now calculate the sum
c
s = a + b
c
c Print out the results with a description
c
print *, 'The sum of ', a,' and ' , b
print *, ' is ' , s
stop
end

I think the "stop" or "read"lines should keep the console waiting for a user action before exiting.
As said, I'm not a specialist on programming languages, but the end user said me that this example progam is running problemless on other computers.

I think the problem is this VFHieEditor.dll wich I can't find anywhere on my harddisk after installation...

[Steven_L_Intel1]

VFHieEditor.dll is part of version 10 or later, and is unrelated to whatever issue the user has. There is nothing wrong with the VS integration and the repair tool you have was built for version 10 or later. STOP will cause the program to cease execution and, if running under the debugger, the output window will disappear. The program will pause at the READ but that's before the program computes the output.

The behavior the user describes is what is expected. Anthony's suggestion is correct - set a breakpoint at the END statement if running under debug, or use "Start without debugging" to leave the console window up after the program exits.

[Les_Neilson]

You can safely ignore the "no symbolsloaded" messages.It onlymeans that there are no debug symbols from those dlls. So there is no need to run the repair tool.

The message "The program '[752] Console3.exe: Native' has exited with code 0 (0x0)." shows that the program ran without any errors.

If the user is running the program from a command shell then any output messages issued by the program should be visible in the shell window.

If theprogrammer is running the program from within Visual Studio (which appears to be the case from what you have said) then the consolewindow will dissappear when the program finishes. Any messages printed by the program do NOT go to the "output window"

In that situation the easiest way to keep the console window openis for the programmerto put a breakpoint on the last line of the program, and then run the program. Execution will pause at the breakpoint and the seperate console window will be available for the programmer to examine.

Les

[jgavill]

Thank you for your answers.
I will test and submit to the programmer.
Jol