Debug a C# COM object from VS 6.0 C++ client

[Craig]

I've been writing C# code for maybe as much as 2 weeks now. The code I'm
writing is exposed as a garden variety COM object that VC++ 6.0 and VB 6.0
can use. Coincidentally my COM development track record is also 2 weeks
long. :-) The time has come to debug down into the C# COM object from a
VC++ 6.0 dll. How do I get into the COM object's code. I can use the VC++
6.0 debugger to get into the VC++ 6.0 code but after that I am lost. Help!
Thanks.

Craig

[Dan Bass]

Craig,

There's an option in the Visual Studio .Net to allow debugging for unmanaged
code.
If you go to project -> properties -> debugging. There's an option for
"Enable Unmanaged Debugging".
What I'd do is then import the VS 6.0 project and run the client from here.

If this is not an option, then what you can do is open the COM exposed .Net
assembly in VS.Net, as well as the VS 6.0 client application. Start the
client application, then run the .Net application, which you can connect to
the process you started with VS 6.0.

Hope that helps.

Daniel.

"Craig" <WeeksAtSprynetDotCom> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...

I've been writing C# code for maybe as much as 2 weeks now. The code I'm
writing is exposed as a garden variety COM object that VC++ 6.0 and VB 6.0
can use. Coincidentally my COM development track record is also 2 weeks
long. :-) The time has come to debug down into the C# COM object from a
VC++ 6.0 dll. How do I get into the COM object's code. I can use the
VC++
6.0 debugger to get into the VC++ 6.0 code but after that I am lost.
Help!
Thanks.

Craig

[Craig]

This turned out to be *really* easy with Visual Studio .Net. I just start
up the old C++ 6.0 application and connect to it's process from VS .Net.
Then I can set breakpoints in both the 6.0 and the .Net source code. Sweet.

Craig

"Dan Bass" <Not Listed> wrote in message
news:%2******************@TK2MSFTNGP14.phx.gbl...

Craig,

There's an option in the Visual Studio .Net to allow debugging for unmanaged code.
If you go to project -> properties -> debugging. There's an option for
"Enable Unmanaged Debugging".
What I'd do is then import the VS 6.0 project and run the client from here.
If this is not an option, then what you can do is open the COM exposed ..Net assembly in VS.Net, as well as the VS 6.0 client application. Start the
client application, then run the .Net application, which you can connect to the process you started with VS 6.0.

Hope that helps.

Daniel.

"Craig" <WeeksAtSprynetDotCom> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...

I've been writing C# code for maybe as much as 2 weeks now. The code I'm writing is exposed as a garden variety COM object that VC++ 6.0 and VB 6.0 can use. Coincidentally my COM development track record is also 2 weeks
long. :-) The time has come to debug down into the C# COM object from a VC++ 6.0 dll. How do I get into the COM object's code. I can use the
VC++
6.0 debugger to get into the VC++ 6.0 code but after that I am lost.
Help!
Thanks.

Craig