Shawn, I guess that maybe apart from using COM interop to do it "the old way", Remoting is the way to go here. It will only take a couple of lines of code to publish an object.
Just don't forget to override InitializeLifetimeService() to return null, else your object will be destroyed after some minutes. -Ingo Author of "Advanced .NET Remoting" http://www.dotnetremoting.cc -----Original Message----- From: Shawn Wildermuth [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 7:32 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Per Machine Singleton... I mean one (and only one) instance of an object for each client and process. I had implemented it as an all static class (in-proc singleton), but now I realize that I need one instance per machine. Thanks, Shawn Wildermuth [EMAIL PROTECTED] > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]] > On Behalf Of franklin gray > Sent: Monday, April 29, 2002 1:26 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Per Machine Singleton... > > > what do you mean by Per machine? As in having an object on > the server for each client, or having an object on each > client, but only one object? > > -----Original Message----- > From: Shawn Wildermuth [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 11:57 AM > To: [EMAIL PROTECTED] > Subject: [DOTNET] Per Machine Singleton... > > > I searched through the archives and found one discussion > about this, but it referred to a solution that wasn't posted > anymore. Is remoting my only solution to a Per Machine Singleton? > > Thanks, > > Shawn Wildermuth > [EMAIL PROTECTED] > http://adoguy.com > http://shawnwildermuth.com > > "...for the programmer, as for the chef, the urgency of the > patron may govern the scheduled completion of the task, but > it cannot govern the actual completion. An omelette, promised > in two minutes, may appear to be progressing nicely. But when > it has not set in two minutes, the customer has two > choices--wait or eat it raw. Software customers have had the > same choices. The cook has another choice; he can turn up the > heat. The result is often an omelette nothing can > save--burned in one part, raw in another.... " - Brooks, The > Mythical Man-Month. > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > > You can read messages from the > DOTNET archive, unsubscribe from DOTNET, or subscribe to > other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
