Andrew,
Do you need to expose this functionality to COM? If so, then you will
have to do this through COM+, setting the object pooling properties so that
you access the same shared object, and that the object doesn't die for a
very long time (you have to determine what the appropriate lifetime is).
If you only need .NET clients to attach to this, then I would recommend
you use remoting, creating a singleton server object.
You can not create an ActiveX EXE through COM interop in .NET.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"andrewcw" <an******@acw.com> wrote in message
news:43**********************************@microsof t.com...
With a Multi-USe COM DLL object another applic. can get reference to
it. -
And if that DLL's counter continue to have a least one reference, then
another application or reference to the DLL can exchange info with that
DLL.
Could See the data in the DLL if the DLL exposed it ( like a list ).
What design pattern allows me similar functionality in .NET ?? - and is
there an ability to keep the "OBJECT" runnning if the reference count goes
to
0 ??
--
Andrew