Re: Debugging thru AxHost
- From: "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
- Date: Wed, 7 Mar 2007 13:44:11 +0200
Try to show a message box from the ocx (when it is called by the client app).
While this message box is shown, break into debugger, check the call stack
and switch to a stack frame that belongs to the ocx. Will the debugger be able
to show you the ocx' sources in this case?
Yes in this case the Debugger shows the VB6 ocx source in VB.Net. But
I want step into VB6 Ocx control.
How I have to step into VB6 ocx.
I am not sure it's possible to step between VB.NET and VB6 code in this case,
AFAIR breakpoints always had to be used as a workaround.
Btw, do breakpoints work now? (e.g. if you set breakpoint in the source that has been
shown by the debugger, e.g. in a place that will be executed after you dismiss
the message box)
Oleg
.
- Follow-Ups:
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- References:
- Debugging thru AxHost
- From: Manoharan
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Re: Debugging thru AxHost
- From: Oleg Starodumov
- Re: Debugging thru AxHost
- From: mano
- Debugging thru AxHost
- Prev by Date: Re: Debugging thru AxHost
- Next by Date: RE: Can't single-step
- Previous by thread: Re: Debugging thru AxHost
- Next by thread: Re: Debugging thru AxHost
- Index(es):
Relevant Pages
|
Loading