I have a C# executable file that calls into a Fortran DLL that I created in CVF.
I can debug the DLL in Visual Studio 6 by using the technique given in the documentation: I enter the path to the C# executable file in "Executable for debug session:" in the General category of the Debug tab of Project Settings in VS6, and then start debugging.
However I can?t simultaneously debug the managed code. I can step into the managed code in VS6 but it only appears in the Disassembly window. I tried putting the .pdb files from my VS7 project into the debug folder for VS6 but that didn?t help.
In VS7 there is a feature on the Tools menu called "Debug Processes" that I tried to use, but it doesn?t let me attach to the C# executable. It indicates that the C# executable process is already being debugged by "Unknown Win32 Debugger."
We have been able to debug Fortran and managed code simultaneously when they run in separate processes as EXEs, communicating by an inter-process communication method. The Fortran debugs in VS6 and the managed code debugs in a simultaneous VS7 session; you can single-step from one into the other. What I would like is to do something like this when everything runs in a single process.
Does anyone have a solution that would enable me to debug simultaneously both unmanaged code and managed code running in a single process?
