I've got a server activated object (SAO), in singleton mode (hosted in a 
server Console application on same machine as client).  On the client, I can 
instantiate serveral instances via Activator.CreateInstance, and each 
instance maintains its own state correctly (via properties on the object). 
This is what I want!  However, it's not the way I understand and read that 
Singletons are supposed to work (all mention of it indicates that state will 
be shared across ALL instances).

Can anyone confirm that I can rely on this stateful type of operation?

Thanks.

P.S. I'm using .NET 2.0.

On Aug 9, 6:17 pm, "Krip"  wrote:


> I've got a server activated object (SAO) [...] via Activator.CreateInstance,


Isn't Activator.CreateInstance() only for CAOs? I think you should
Activator.GetObject(). Here's a basic tutor:
http://www.codeproject.com/csharp/dotnetremotingbasictutor.asp

Right, we might be doing CAOs even though we configured for SAOs.  That 
matches with the behaviour we're seeing.  Thanks for the insight.