What is your objection to remoting/web services? I'm sure we could come up with a way to do it, but it's going to be more or less the same as what remoting does - an endpoint of some sort will be exposed, and the object will be hooked up to it. The difference being that you'll be the one that has to write all the infrastructure.
There's certainly not going to be a way to just sort of magically reach over and touch the object in another process. What are you trying to do? If it's just info sharing, maybe you can always write to a file in a well-known location. > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]] On Behalf Of > Alex Henderson > Sent: Monday, April 22, 2002 7:40 PM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Attaching to a windows service.. > > > If I have a class instantiated in a window service, can > another program on the same machine get a reference to the > class instance in the windows service's thread and call its > methods ... I don't really want to use remoting/web services > if possible. > > Additionally are there any good on-line resources discussing > multi-threading etc. in the .Net framework that might point > me in the right direction. > > Cheers, > > - Alex > > You can read messages from the Advanced DOTNET archive, > unsubscribe from Advanced DOTNET, or subscribe to other > DevelopMentor lists at http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
