"Instead of trying to debug from vs.net, we tried to debug the dll source
from vb 6, by starting the dll with run, in debug mode.
After this, i've removed the original reference to vb dll, and added the
reference to .vbp in vs.net. while vb is in debug mode."
Just to clarify, did you try to debug
2003 9:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] A complicated debug scenario
Hi Seref:
i recently had the same frustration as you debugging my ASP.NET web
service and then on into my vb6 COM DLL. after much much frustration and
research, i was actually willing to expire an MSDN in
] On Behalf Of Ben Callister
Sent: Wednesday, July 02, 2003 2:03 PM
To: [EMAIL PROTECTED]
Subject:Re: [ADVANCED-DOTNET] A complicated debug scenario
Hi Seref:
i recently had the same frustration as you debugging my ASP.NET web
service and then on into my vb6 COM DLL. after much much
callister
[EMAIL PROTECTED]
-Original Message-
From: Seref Arikan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 02, 2003 10:39 AM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] A complicated debug scenario
Hi,
Currently i'm trying to implement a com interop project.My business
Hi,
Currently i'm trying to implement a com interop project.My business logic is
implemented in a vb com dll, which i access from asp.net via com interop
Today, we had a serious problem and tried to debug the dll source. Even if i
managed to debug the vb dll from inside vs.net, the debugger acted s
