Hi,

I have have a .NET application that is running out of memory. We suspect a
memory leak in one of the COM components the application is calling. To try
to isolate this, I thought I would try running the COM DLLs out-of-process in
the standard surrogate, DLLHOST.EXE. To do this, I've created a new GUID,
used this to add an AppID entry under HKCR/AppID, added an empty DllSurrogate
REG_SZ, and linked the COM component's HKCR/CLSID key to the newly created
AppID through an AppID REG_SZ. However, the COM component is still being
loaded in process - there are no DLLHOST.EXE processes created at all when I
debug my .NET application. I've even tried using dcomcnfg to tell the COM
component to run as a different user, but I still don't get a DLLHOST.EXE
process.

Can anyone tell me what I'm doing wrong? Is it possible to force an in
process COM DLL to run out-of-process when it is being called from a .NET
application?

Also, while I'm here, does anyone know if it's possible to get Visual Studio
.NET 2003 to show COM DLLs in the modules window? Or indeed how to step into
such a DLL in the dissembly view?

Thanks,
- Lee