Re: Best way to debug VB6 and VB.net interop
- From: "Egbert Nierop \(MVP for IIS\)" <egbert_nierop@xxxxxxxxxxxxxx>
- Date: Sun, 11 Sep 2005 11:23:59 +0200
"Robert Jordan" <robertj@xxxxxxx> wrote in message news:dft07v$c39$00$1@xxxxxxxxxxxxxxxxxxxx
Hi Eric,
Thanks for the help. That worked great. If you don't mind I have another weird debugging situation. What is the best way to debug a VB.net dll calling a VB com dll? I have a VB6 app that is calling a VB.net dll that then calls a VB6 dll. I don't care about debugging the VB6 app so I just set that as the start up of teh VB.net dll and I can debug the VB.net dll. I have the VB6 dll running in the Vb IDE but the breakpoiunts don't stop in the VB6 dll. Is this the correct way or is there something else?
Sorry, I don't know much about VB6. You may try the same trick using something similar to .NET's Debugger.Break.
This is indeed similar.
You should do a
declare Sub DebugBreak lib "Kernel32"()
Compile the VB6 class with 'include debug symbols'.
In this case, you can't use 'edit & continue' in VB6, the VB6 Ide can't be used to debug, the debugger IDE will jump into to the VB6 DLL and show the VB6 source code.
Rob
.
- Follow-Ups:
- References:
- Best way to debug VB6 and VB.net interop
- From: Eric
- Re: Best way to debug VB6 and VB.net interop
- From: Robert Jordan
- Re: Best way to debug VB6 and VB.net interop
- From: Eric
- Re: Best way to debug VB6 and VB.net interop
- From: Robert Jordan
- Best way to debug VB6 and VB.net interop
- Prev by Date: Re: Iterating through collection from VB6 gives error 424 Object r
- Next by Date: Re: Use com objects or .NET remoting?
- Previous by thread: Re: Best way to debug VB6 and VB.net interop
- Next by thread: Re: Best way to debug VB6 and VB.net interop
- Index(es):
Relevant Pages
|