i am trying t.o troubleshoot an app in vc6. c++ which imports a few .net
dll's. The tli,tlh's are created from tlb's and I am off and running.
Problem is, I am playing a guessing game about where the app is failing. It
is neither an art or a science. I make sure the .NET components and code
works in vsnet which they do. But when I go into the older IDE and launch
the app, I simply can't step thru the debugger once I leave the VC++ code.
I can only see the interface method where the .NET method is called. Beyond
that, with respect to what THAT method is calling and where it runs into a
problem, i have no clue.
when i worked in vc++ years ago, you could attach to a process. can you do
that with a .net process? thx. -greg
hazz - 21 Sep 2004 17:58 GMT
solved the debugging problem. found out troubleshooting with interop is an
art. ;-)
> i am trying t.o troubleshoot an app in vc6. c++ which imports a few .net
> dll's. The tli,tlh's are created from tlb's and I am off and running.
[quoted text clipped - 7 lines]
> when i worked in vc++ years ago, you could attach to a process. can you do
> that with a .net process? thx. -greg