Remoting between applications on the same machine
-
Hi I have two .net applications running on the same PC. (its a long story.) I need to do a little bit of communication. I've read that Remoting is the way to do this, but all the examples for remoting involve three applications where one is a server, and tcp connections, and complicated stuff I don't need. Is there like a simpler thing I can do? "Outside of a dog, a book is Man’s best friend. And inside of a dog, it’s too dark to read." -Groucho Marx
-
Hi I have two .net applications running on the same PC. (its a long story.) I need to do a little bit of communication. I've read that Remoting is the way to do this, but all the examples for remoting involve three applications where one is a server, and tcp connections, and complicated stuff I don't need. Is there like a simpler thing I can do? "Outside of a dog, a book is Man’s best friend. And inside of a dog, it’s too dark to read." -Groucho Marx
Bog, Let me suggest the following book on remoting: "Advanced .Net Remoting" C# Edition by APress ISBN 1-59059-025-2 You can implement remoting between your two applications without the need of a "server" application. This means that your two applications each act as a client and a server to each other. This requires that each application in acting as a server must be on a different port number. Beware of UI Controls responding to remoting calls as they are handled on a seperate thread. UI control methods can only be accessed by the "creator" thread which is the application thread. While Remoting in .Net is made simple, it still requires a good understanding of the details to build proper remoting components. Happy coding!
-
Hi I have two .net applications running on the same PC. (its a long story.) I need to do a little bit of communication. I've read that Remoting is the way to do this, but all the examples for remoting involve three applications where one is a server, and tcp connections, and complicated stuff I don't need. Is there like a simpler thing I can do? "Outside of a dog, a book is Man’s best friend. And inside of a dog, it’s too dark to read." -Groucho Marx
If you want two way communication where each app can talk to the other one, you need to start remoting servers on both applications, and whenever you want to talk to the other app from the current app, make a remoting client connection to the server (that's all). The examples you see use only 2 applications (but 3 or even 4 VS.NET projects for the shared class library and the interface library) Nish
Extending MFC Applications with the .NET Framework [NW] (My book with Tom) Summer Love and Some more Cricket [NW] (My first novel) Shog's review of SLASMC [NW] Come with me if you want to live