- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
after compiling my dll in IVF i copied the .dll and .pdb to the bin folder of my vb project. debug format information is 'Full (/Zi) in the property page for the dll project.
i'd like to be able to step through the fortran code during a debug session of the vb application. in the vb ide, i pause at the line before the fortran library call, then step into (F11). no fortran, just successful completion of the fortran subroutine.
i know the dll is the correct one as i wrote a new message in my fortran to my fortran debug file.
thanks in advance for any help!
i'd like to be able to step through the fortran code during a debug session of the vb application. in the vb ide, i pause at the line before the fortran library call, then step into (F11). no fortran, just successful completion of the fortran subroutine.
i know the dll is the correct one as i wrote a new message in my fortran to my fortran debug file.
thanks in advance for any help!
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
compiling the IVF dll (with output going directly to my VB bin folder) from within a VS2005 solution that contains my VB and fortran leads to more files in the VB bin folder (.dll, .dll.embed.manifest, .dll.embed.mainest.rc, .dll.intermediate.manifest, .exp, .lib). no new .pdb.
in a pane in the VS IDE showing the hoped for breakpoint in my fortran code is a triangle/explanation with a tooltip saying 'The breakpoint will not currently be hit. No symbols have been loaded for this document.'
in a pane in the VS IDE showing the hoped for breakpoint in my fortran code is a triangle/explanation with a tooltip saying 'The breakpoint will not currently be hit. No symbols have been loaded for this document.'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In ordinary circumstances, all you would need to do is set Debugging > Enable Unmanaged Code Debugging in the VB project properties to "Yes". However, I don't know if this is available in VB Express and I know that there is no Fortran integration into VB Express's IDE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Setting Debugging > Enable Unmanaged Code Debugging in both the VB startup project and the VB project calling the fortran does the trick in VS2005. That will work for us.
Thanks for your help!
Thanks for your help!
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page