Re: How to debug a VB com+ is call from ASP.NET Webservice
- From: "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
- Date: Tue, 27 Feb 2007 09:41:33 +0200
I need to debug a com+ dll and VB 6.0.
If use an VB.NET Application Project works fine, but when I'm using a
VB.NET ASP.NET webservice then debugging is not working.
So I like to ask how i can do this.
Here is one possible approach:
- When compiling the VB6 dll, enable compiling to native code
and debug information generation (if I remember it right, these settings
are called "Compile to native code" and "Create symbolic debug info"),
also consider disabling optimizations
- Attach VS debugger to the process that hosts the VB6 dll (make sure that
you select the native debug engine when attaching (in VS2005 you have to
use Select button in Attach to Process dialog to do that))
- Open VB6 source code and set breakpoints
A problem with this approach is that debug information produced by VB6
can omit some important variables (and thus the debugger will not be able
to show them). Possible solutions are to use tracing (trace the values of those
variables to debug output, using VB6 means) or introduce some temporary
local variables and assign to them the values of the problematic variables
(because local variables are usually shown correctly by the debugger).
--
Oleg
[VC++ MVP http://www.debuginfo.com/]
.
- References:
- How to debug a VB com+ is call from ASP.NET Webservice
- From: thaispookie
- How to debug a VB com+ is call from ASP.NET Webservice
- Prev by Date: Re: Program crashes when running accross network, but fine when on pc
- Next by Date: MiniDumpWriteDump fails when using dump type MiniDumpWithIndirectlyReferencedMemory
- Previous by thread: How to debug a VB com+ is call from ASP.NET Webservice
- Next by thread: Re: Program crashes when running accross network, but fine when on pc
- Index(es):
Loading