If this works at all, I am certain that it only works with unmanaged DLLs
developed with .Net studio!
In my case the DLL is still being compiled with Developer Studio 6 while I
am doing new development in .Net, and it does not seem to permit me to cross
the DLL boundary in the debugger.
-Ken
"Sam Gentile [MVP - C#/.NET]" <no****@nomail.com> wrote in message
news:u7**************@TK2MSFTNGP12.phx.gbl...
If I remember correctly, with VS.NET you should be able to step into the
unmanaged code from the .NET code if you set "Native" as well as the
managed setting.
--
----------------------------------
Sam Gentile
MVP - C#/.NET
INETA Speaker http://www.ineta.org/DesktopDefault.aspx
Read my blog at http://samgentile.com/blog/
------------------------------------------------------
"Ken Allen" <ke******@sympatico.ca> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl... I have a managed .Net assembly (C#) that invokes code in an unmanaged
DLL written in C++ 6 via an unsafe assembly that invokes the C++ routines
and marshals the data. The interface is not working properly.
Is there a way to have the C++ 6 debugger running on the unmanaged DLL when it is invoked from the .Net debugger? I cannot step into the DLL, but
can I access it via a separate debugger?
Or am I left with instrumentation as the only debugging tool?
-Ken
