We have an ongoing problem debugging our ServicedComponent. This is a
follow up to the thread entitled: "Unable to debug interop". I want to
restate the issue because in that previous thread, we solved one
problem, we now have another separate problem.

We have an existing VB6 Application named CAT
CAT calls a series of COM objects written in VB6, I'll call this (COM
OJBs)
One of the COM OBJs eventually invokes our ServicedComponent.dll which
is registered for COM, regasm. This is named CImportHandler. So
CImportHandler is invoked in process. All of this by the way occurs
within the same COM+ transaction.

Therefore, CAT -> COMOBJs -> CImportHandler (ServicedComponent/DLL)

We need to debug CImportHandler in VS.NET.

------------------------
We CAN debug CImportHandler given the following:

DemoApp (VB6) -> CImportHandler

However, this only proves that the debugger works when COM+ is not a
factor.
--------------------------------------------
We have tried:

1. Project | Properties | Configuration Properties | Debugging
2. Setting Debug Mode to Program
3. Setting Start Application to the CAT program
4. Setting the Working Directory to CAT's working directory

When we debug, CAT is loaded. The breakpoint looses the question mark
when the component is loaded (which can be observed by watching the
modules list) but everything hangs right after

System.EnterpriseServices.Thunk.dll 79620000-79636000
C:\WINNT\assembly\GAC\System.EnterpriseServices\1.0.5000.0__b03f5f7f11d5
0a3a\System.EnterpriseServices.Thunk.dll 174 1.01.4322.2032 [1400]
CCFAutoTester.exe: Native 7/15/2004 12:43 AM No symbols loaded.

We've even tried to attach to DLLHOST.EXE after starting this debugging
session so that both CAT and DLLHOST.EXE show as attached in the
Processes List. This accomplished nothing.

--------------------------------------------
We have tried

1. Project | Properties | Configuration Properties | Debugging
2. Setting Debug Mode to Program
3. Setting Start Application to the DLLHost.exe
4. Setting the Command line to /ProcessID:{our process id}

This of course does nothing because it is CAT which initiates the COM+
transaction. Plus, from what I've read, one would only do this if
dealing with a com server which ours is not.

Any help, insight, pointers, etc would be greatly appreciated.

-- xavier