We want to set up ONE shared .NET server with VB.Net that
shall expose ONE shared singleton instance to all requests.
This instance has to be exposed to COM, too.

While it is no problem to access the server with .NET
remoting from a .Net client, accessing it from a COM-Client
(VB) starts a new .Net server process with each request.

How can we make sure that there's only one process serving
all requests?

Thanks for any suggestions.

Falk.