> How to debug VB6 Activex Usercontrol (ocx) hosted in VB.Net container.
>

wrote:
> > How todebugVB6Activex Usercontrol (ocx) hosted inVB.Netcontainer.
>
> Try the approach described here:http://groups.google.com/group/microsoft.public.vsnet.debugging/brows...
>
> --
> Oleg
> [VC++ MVPhttp://www.debuginfo.com/]

> 1. I created a test VB6 Ocx control with create symbolic debug info
> and disabled optimizations.
> 2. Register the control using regsvr32
> 3. created a test VB.net application & hosted the registerd control in
> the form enabled the Unmanaged code debug.
> 4. Ran the VB6 ocx application
> 5. Then ran the VB.Net application
>
> It hangs it won't go the break point i have set in the VB6 ocx
> control.
>

wrote:
> > 1. I created a test VB6 Ocx control with create symbolic debug info
> > and disabled optimizations.
> > 2. Register the control using regsvr32
> > 3. created a test VB.net application & hosted the registerd control in
> > the form enabled the Unmanaged code debug.
> > 4. Ran the VB6 ocx application
> > 5. Then ran the VB.Net application
>
> > It hangs it won't go the break point i have set in the VB6 ocx
> > control.
>
> If it really hangs, break into debugger and check what it is doing.
> If it works but does not hit breakpoints in VB6 code, open Modules window
> and check if the ocx is loaded, and if its symbols have been loaded.
>
> Oleg

wrote:
> > 1. I created a test VB6 Ocx control with create symbolic debug info
> > and disabled optimizations.
> > 2. Register the control using regsvr32
> > 3. created a test VB.net application & hosted the registerd control in
> > the form enabled the Unmanaged code debug.
> > 4. Ran the VB6 ocx application
> > 5. Then ran the VB.Net application
>
> > It hangs it won't go the break point i have set in the VB6 ocx
> > control.
>
> If it really hangs, break into debugger and check what it is doing.
> If it works but does not hit breakpoints in VB6 code, open Modules window
> and check if the ocx is loaded, and if its symbols have been loaded.
>
> Oleg

> I found the way to opne the Modules window.
>
> 1. I ran the VB6 ocx control
> 2. attach the process to VS2005 debugger
> 3. I have opened the modules window bu the ocx & its symbol file is
> not loaded.
>

Also, previously you wrote:

> 1. I created a test VB6 Ocx control with create symbolic debug info
> and disabled optimizations.
> 2. Register the control using regsvr32
> 3. created a test VB.net application & hosted the registerd control in
> the form enabled the Unmanaged code debug.
> 4. Ran the VB6 ocx application
> 5. Then ran the VB.Net application

> > In VB.NET application, set breakpoint at some place where you absolutely
> > sure that the ocx will be loaded. After that breakpoint is hit, check the presence
> > of the ocx and its symbols in Modules window.
>
> I did the above step & the ocx control is loaded and its symbol is al
> lodaded.
>
> This is the line I copied from the modules window.
>
> "DebTest.ocx D:\debug test\DebTest.ocx N/A N/A Symbols loaded. D:
> \debug test\DebTest.pdb 33 1.00.0.0 3/6/2007 5:28 PM 11000000-11006000
> [3172] W.exe: Native "
>
> I have set break point in the ocx also but it is not hiting the break
> points of the ocx control.
>

> > 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.
>

> In VB.NET application, set breakpoint at some place where you absolutely
> sure that the ocx will be loaded. After that breakpoint is hit, check the presence
> of the ocx and its symbols in Modules window.

wrote:
> > > In VB.NET application, set breakpoint at some place where you absolutely
> > > sure that the ocx will be loaded. After that breakpoint is hit, check the presence
> > > of the ocx and its symbols in Modules window.
>
> > I did the above step & the ocx control is loaded and its symbol is al
> > lodaded.
>
> > This is the line I copied from the modules window.
>
> > "DebTest.ocx D:\debug test\DebTest.ocx N/A N/A Symbols loaded. D:
> > \debug test\DebTest.pdb 33 1.00.0.0 3/6/2007 5:28 PM 11000000-11006000
> > [3172] W.exe: Native "
>
> > I have set break point in the ocx also but it is not hiting the break
> > points of the ocx control.
>
> 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?
>
> Oleg- Hide quoted text -

wrote:
> > > 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