Can't debug dynamically loaded DLL? -- dotnet academic

DotNetJunkies User
6/23/2004 3:22:50 PM

I have a pure C++ project in .net 2003 with a main EXE and many DLL subprojects. I can step into those sub DLL projects that are linked explicitly with the main program without problems. But for those DLL's that are loaded dynamically loaded via LoadLibrary, .net seems to ignore them altogether. When I set a breakpoint in one of those source files, .net didn't break. When an exception occurred in those DLL's, the stack trace shows up. But when I double click on the stack frame that's in one of those DLL's, .net tells me that the soure code is not available.
Is there a trick to do this? Any help is much appreciated.

---
Posted using Wimdows.net NntpNews Component -

Kyle Prestenback [Microsoft MVP]
6/23/2004 8:04:01 PM

BEfore you execute your application, does the breakpoint have a '?' on it? and after you perform LoadLibrary, does it become solid? If so, things are going correctly.

Perhaps you are accessing an older version of the dll in your application, which would lead the application to not execute those break points.

Another suggestion, In your applications properties page, on the Debugging menu, set the debugging type to mixed or native.

Kyle
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet academic

dotnet academic : Can't debug dynamically loaded DLL?