Cannot step into unmanaged code from managed code

  • Thread starter Thread starter Smith
  • Start date Start date
S

Smith

I have a project with an unmanaged ATL Smart Device project and a .NET CF
PocketPC 2003 SE application.
I cannot step into my unmanaged COM object's code from the .NET application.

Is managed-to-unmanaged debugging supported or not with Visual Studio .NET
Beta2?

Thanks.
 
AFAIK step-through is not supported. You should be able to debug either
managed or unmanaged.
 
Actually step into is not supported with Smart Devices _at all_ (with VS
2005 Beta2 at least).
If I create an MFC application in a first project, have another ATL DLL
project and set up a reference between the two, I will still be unable to
step into the ATL DLL code.

(Meaning that I really don't know how to debug ATL libraries)
 
Not true. You could do this even in eVC 3. All you need is to tell debugger
to preload DLL's symbols (iin the project properties "Load these additional
DLLs")
 
I can see this with eVC 4 in the project settings.
With VS .NET 2005 Beta2 I don't see anything like that.
Looks like a bug, or worse: a limitation.
That's pretty bad because I can't think of a workaround.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Unmanaged code calling managed code via COM? 1
mixing unmanaged and managed c++ code 2
Importing Structure of Unmanaged DLL to managed code 1
Newbie: MissingMethodException error with managed/unmanaged C++ 1
Debugging from Managed Code into unmanaged code 2
Using unmanaged code from CF 1
Debugging unmanged code (C++) from a managed project (C#) 1
Deploying unmanaged DLL. 1

Back
Top