The saga continues. Sometimes I think I must be the first person in the world to convert a VB6 project that calls a VC++ DLL into the new and exciting (ie really irritating) .net versions, namely vb.net and vc++.net
In VC++ 6.0 you could set the debug version of the calling VB6 .exe and then trace it through the dll step by step like this:
Project --> Settings --> Debug --> Executable for Debug Session
Now,according to Microsoft you cannot do this in 2010 Express version of vc++.net but you CAN (they say) put a break in the vc++.net dll then start your exe in vb.net and it will step into it
Well, when I try it, it does NOT go into the DLL when I press F8 - anybody know the trick?
(I am using 2010 Express because I am on XP because I still need VB6 and it will not install the VB6 IDE in Win 7/8)
Edit:
Well, it seems that in vb.net, if you right click when you get to the line of code that calls the function in your dll, you get the following option (in my case):
Step Into Specific: MOPEKS.prjDLLs.TestF
where "MOPEKS.prjDLLs" is the module in my code that includes TestF. So, I do this and press it, whereupon, according to Microsoft it should go into the function TestF. Of course, it doesn't but this does sound like progress of a sort
Here is MS on the subject from:
http://msdn.microsoft.com/en-us/libr...=vs.90%29.aspx
To step into a specific function
Advance the execution point to the function call you want to step into. (You might use a breakpoint, Step Into, Step Over, or Run To Cursor.)
Right-click the source window to open the shortcut menu.
Click Step Into Specific and choose the function you want from the submenu.
The debugger executes the function call and breaks at the beginning of the selected function. The Step Into Specific command appears only if the execution point is located on a line of code that contains a nested function.
I have a horrible feeling that maybe it is disabled in the Freebie versions (ie Express 2010 in my case)