Debug .NET 2.0 VS2008 "Class Library" accessed by COM

Due to different output results between my .NET caller (test exe, from inside
the solution) and my production COM caller, I would like to debug my .NET dll
(with COM interface) when using the COM caller application.

I was unable to attach to the caller's process (Siebel 7 / IE6).
I remember that VB6 offered the solution "Wait for components to be
created". Is there something similar available in VS2008?

-I'm using VS2008 (framework 2.0), C#
-COM caller is Siebel 7 (inside IE process)

Any help would be appreciated!
.

Relevant Pages

  • Re: TAPI Browser refresher/quick tutorial
    ... debug, stopping at the first call & examining it, ... Bryan Dickerson wrote: ... My problem wasthat all the caller ids were coming ... > up with the internal number for the voicemail system instead of the external ...
    (microsoft.public.win32.programmer.tapi)
  • RE: name of calling function
    ... my $caller = caller; ... calling info away. ... sure that some operation happens after the call to your debug() method. ...
    (perl.beginners)
  • Re: Memory Leak Detection (again?)
    ... This waffle probably won't help you (and its mainly to do with detecting leaks within a C library where the caller has to be careful about freeing the internals of structures that the caller may not have directly allocated) but.... ... The debug version would then look like ...
    (microsoft.public.vc.mfc)
  • Re: Can a function determine what file and line of source in that file called it?
    ... > To assist in debug I would really like my functions to be able to issue a ... > point me to the appropriate documentation? ... perldoc -f caller ...
    (comp.lang.perl.misc)
Loading