- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have been able to run both with and without debugging: console applications, DLL's, and anything else. Yesterday, however, I received the following error message on my Visual Studio 10 screen when trying to debug a DLL: "Unable to start program: 'myProg.exe'. The system cannot find the file specified." (where myProg.exe is the program that is meant to call the FortranDLL). However, I CAN run the program without debugging (i.e. control-F5). Only clicking F5 produces the error message. This happened with two different DLL projects of mine. If I then open a console application project (one that produces an EXE file), the debugger works fine. And now the clincher: I CAN debug those DLLfiles if I open the specific solution from the command line (i.e. I click on myDLL.sln in Windows Explorer). Then Visual Studio opens with the solution ready to go. Then, when I press F5 or click the debug icon, it debugs as usual. However, once Visual Studio is open and I open the project from the menuFile-Open or from File-Recent Projects and Solutions, then the DLL's can no longer be debugged during that session, but can be run without debugging. I am using Fortran Compiler XE 12.1. Any help would be greatly appreciated.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since the EXE file was in my working directory, I saw no need to include the path when enering its name. Once I included the full path, the debugger started with no problem.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page