Out of process COM server accessible by a client embedded in IIS

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: KoolMo (ramui123_at_hotmail.com)
Date: 04/23/04 

Date: Fri, 23 Apr 2004 09:26:06 -0700

Hi All,
maybe I ain't posting to the right newsgroup and if so please point me to the right one and accept my apologies.

I desperately need to extend an existing win32 application to have it behave as an out-of-process local server by exposing the content of some of its objects via COM interfaces to a IIS Server Side Component or to JScript calls in an ASP page.
The win32 application has its own life cycle and is started and shutdown by a user sitting at the server machine (it monitors embedded devices via serila line) and I need to have IIS (via an ASP page or a dLL component or whatever) access the application (if running) via LPC and collect data on its status.

I have tried everything but can't go any further than having the COM client accessing not the existing instance of my application but it loads another instance of it which doesn't show any window (and fights with the existing one for resources sharing).

I have successfully managed to obtain the desired behavior when a com client is a console application (as got it by adapting the chap10 example in the "inside COM " MSPress book) but can't do anything similar when the client is either the ASP page (using Server.CreateObject("..")) or a ASP server side component into a DLL running in the IIS address space.

Am I missing something? Can anyone please give help or point me in the right direction (maybe a tutorial)?
TIA.
Mo