Debugging a VB-IVF mixed language solution

[jond]

I have a VB.NET (the GUI) and IVF DLL (numerical engine) mixed language solution under VS2005. I would like to be able to debug both the VB and Fortran code, and be able to step into and out of the Fortran DLL. However, when I try to step into a Fortran function from the VB code, the debugger just steps over the Fortran function. The function is operated, the returned value is correct, but I just can't step into the Fortran DLL. In the VB code, the DLL is declared with its absolute path to avoid any "DLL hell" sort of problems, and the debug version of the DLL is copied into this path.

Any ideas on how to succesfully debug such a mixed language solution?

I am using VS2005, VB.NET and IVF 10.1.011.

Thanks,
Jon

[jimdempseyatthecove]

Jon,

Assuming the Fortran DLL was compiled with Debug information it sounds like the symbols for the Fortran DLL were not loaded. As a work around (possibly a once only per debug session thing), place a break point in the VB program at the 1st call to the Fortran DLL and then open a Disassembly window. From the Disassembly window perform a step into (F11) through the call instruction. You may have to step into twice: Once to get to the jmp table, then once again to get to the function entry point. Once there, hopefully the debugger will find the symbol information.

Jim Dempsey

[Steven_L_Intel1]

In the VB project, select the project Properties, Debug and check the box "Enable unmanaged code debugging".

[jond]

Thanks. Checking the "Enable unmanaged code debugging" box worked.

Jon