Best and easiest way to pass data from two EXEs

That is great!

That is much easier than working with .net remoting for simple  same machine tasks.

Thank you very much Alan.

Thank you

I follow your advice and use a file.

If both applications will already have an open connection to SQL Server, then that would be a reasonable way to do it.

Otherwise it's a bit heavy and certainly slower than using a simple text file.

There's nothing wrong with using the clipboard to transfer data between applications but it's not very robust - the user might inadvertently use the clipboard for some other operation before the first application has time to read it.

Remoting is complicated and it can be difficult to get it to work reliably across process boundaries. There's also the newer WCF which is supposed to be easier than remoting but I've never used it and so can't testify to its efficacy.

Thanks Alan

I guess the file solution sounds simpler.

Would it work the same or slower if I just have app 1 update a set of fields in a table and have each application update its value?

is that slower to access in SQL Server 2005?

Right now I actually had it working by writing to the clipboard because I had to get something working for the company but it makes me feel stupid to do it that way.

is .net remoting too complicated for something like this?

thanks

Well, the easiest way is for one application to write values to a disk file which the other application then reads.

The problem, of course, is synchronization. If the first application uses the System.Diagnostics.Process class to launch the second and the second writes values to the file before exiting, the first application can simply wait until the second has exited by calling the Process.WaitForExit() method. It can then read the values from the file and delete it.

Otherwise, it's a matter of polling the file until the values arrive and having a simple way of ensuring that you're reading the latest values if the process is to be repeated.

If this approach is not sophisticated enough for what you need to do, then I'd look at either named pipes or shared memory.

Shared memory is very fast and reliable but it needs a ton of API calls to set up.

Named pipes are a good way of providing two way communication between processes on a single computer as they don't require a network transport and so are quite simple and fast.  The drawback is that they can only deal with streams of bytes (so you need to deserialize to other data types) and you need to decide on some sort of protocol between the two applications so that they don't attempt to write to the stream at the same time.