Reference to an external object/application

Hey,

I'm trying to write a script to run in program 1 that will pull information from program 2, but I can't figure out how to access program 2. The information I have on writing external scripts/applications for program 2 is:

Quote:

---

In order to work with MediaMonkey’s objects from outside a MediaMonkey script, you need to create a reference to the SDB object (an instance of the SDBApplication class) yourself. For external applications, make sure that you have added a reference to the SongsDB library, first.

---

and the example they give is:

Code:

---

SongsDB::SDBApplication^ SDB = gcnew SongsDB::SDBApplication();
 
SDB->ShutdownAfterDisconnect = false;    // in case you want to keep an opened instance open after disconnecting the SDB object

---

I tried putting the example code into my main function, which of course didn't work but I have no idea on what I'm doing. Any help is much appreciated.

Thanks,

redmaw

You can inject a dll into program two and read data from there, or you can send data with Winsock between the two applications. Or you can make program two write to a file, and program one reads data from that file and displays the information. So many ways.

Thanks iPromise. Winsock looks like what I need, although I'm thinking of trying a different language as friend suggested now.

Do modern operating systems allow for a mode where a particular program can have full read access to memory? This way I could check the status of one of my simulations without overhead. Well, maybe.

You cannot access physical memory unless you are in the kernel. And this isn't C++. Just a FYI.

There are many ways to do this. This list assumes you are on a Windows OS:

• Mailslots (essentially a buffer of data that both processes can access)
• A shared file
• A shared port (process A broadcasts data over a port and process B receives it via the port)
• Pipes (read more about this in the Windows SDK) - very simple
• DLL injection

I've done all of these and I prefer to stay away from DLL injection b/c there are so many other elegant ways available to use. However there are things that DLL injection can do that the other methods cannot but based on your post you will not need this functionality.

Mailslots, eh? I'll look into that. Thanks Elysia and Bubba.