Personally, if I needed to do this, I would look at creating a Windows Service application. Then the clients would connect to the service via remoting. For the COM requirement, I would write a small COM enabled DLL that wrapped the remoting infrastructure to talk to the service.
The advantages to this model is that by having a service, you can set the service handler to restart the application if it errors for some reason, it is always running, and there is a defined interface to your background application.
HTH
--
David Williams, VB.NET MVP
[quoted text, click to view] "Chris Langston" wrote:
> Hello--
>
> I've looked for the answer to this question everywhere I
> can think of with no success, and I feel like I'm probably
> missing something very simple.
>
> I'm in the early stages of migrating quite a bit of code
> from VB6 to VB.NET. In VB6, I was able to create an
> ActiveX EXE server that would allow me to maintain
> persistent object data, even during periods when no
> clients were connected, using global variables in standard
> VB modules.
>
> I'm trying to duplicate that functionality in .NET. I
> still need COM support for backward compatibiltiy of some
> clients. Essentially, I'm looking for a way for a client
> to create an object, make changes to soem shared data,
> shut down, and then allow another client access to that
> same shared data at a later time. Is there a way to do
> this in .NET without writing the data out to disk?
>
> Thanks for any insight.
>
> --
> Chris Langston
>