🚀 go-pugleaf

Andrue Cope [TeamB] wrote:

>We have an application that can also be a COM server. The way it is
>coded means that it must be one or the other. IOW if someone has
>launched the application independantly it should be able to tell any
>potential clients to get lost and start another copy.

I'm sorry, Andrue, maybe if I knew anything at all about COM Servers,
this would make sense.... Are you saying....

You have an exe, that when launched as instance 1 (i1), it does what?
Does it behave as an application, or a COM Server, or a self-contained
application that uses COM services?

When instance 2 is launched, what then?

I assume from your question that you want one and only one Com Server
running.  From your first sentence, if the exe can only be one thing,
either an application or a Com Server, then how about using standard
instance controls (mutex,etc.)? When the exe starts, it checks, and if
it is (i1), it becomes a Com Server, and relaunches itself (i2) to be
the application.  Then if the user launches again, (i3) sees the flag
and becomes an application too.

Or, re-reading your Q a 6th time.... Do you want the second
user-started exe to inform the first that another application window
is requested, and then terminate? You could do that a couple ways, use
the mutex, or maybe a pipe, that (i1) sets up, to send the request. Or
fire off an event and then terminate.