You could use the WinDbg program from the Platform SDK and load the SOS
dll file to allow managed debugging. Navigate to the following link for
details:
http://weblogs.asp.net/fmarguerie/archive/2005/02/25/380291.aspx Bryan Phillips
MCSD, MCDBA, MCSE
Blog:
http://bphillips76.spaces.live.com [quoted text, click to view] "jbofemc@gmail.com" <jbofemc@gmail.com> wrote in message
news:1158685402.524426.191430@i3g2000cwc.googlegroups.com:
> I have an x64 project where the EXE is native unmanaged C++ and it
> calls a managed C# DLL. For the Win32 version of the EXE, I'd set the
> debugger type from "Auto" to "Mixed" and this would allow me to debug
> my native C++ application and step into the C#/CLR code in the DLL, but
> when I perform these same steps in the x64 version, I get an error when
> I try to debug the EXE, saying "Unable to start program
> <my_program_name>. The debugger does not support debugging managed and
> native code at the same time on this platform."
>
> Is this a bug? Or is this a known issue?
>
> If this option isn't available, does MS plan to support this?
>
> How does one debug mixed components under Win64?
>
> I can debug my DLL directly and set the target to my EXE (do I'm
> debugging the DLL instead of the EXE), but this on't allows me to step
> through the C# code in the DLL, not the C++ code in the EXE, so I kinda
> have a workaround, but this isn't an ideal situation.
>
>
> BTW: The OS I'm running under is MS Windows Server 2003 Enterprise x64
> Edition SP1, and my development environment is MS VS 2005 Pro
> 8.0.50727.
>
>
> Thanks,
>
>
> Jeff