Sending mesages between C# apps

[Jason]

I've a c# app that I execute on a remote machine, which works as I expect it
to, but when that apps throws an exception on the remote machine how do I
know what's
going on, since it's a remote app?

For instance on the remote app that I execute I check for the existence of a
file, and if it's not there,I want to display a simple popup message telling
the user that the file doesn't exist on that machine and then I quit the
app. How do I send a message, back to the user that started the remote app?

Any ideas, or examples?

 

[garyusenet]

You need to check out .net 'remoting'

 

[Steve Drake]

Look at WCF.

Its part of .NET Framework 3.

Just google in, or live it.

Steve

http://stevesdotnetblog.spaces.live.com/

 

[Thomas T. Veldhouse]

You need to check out .net 'remoting'

And allow remote debugging via attaching to the remote process [like dllhost
or svchost or whatever it happens to be].

 

[V]

You need to check out .net 'remoting'

I'm not the O.P., but I have a related question: What is the usual way
of communicating between a C# app and an unmanaged C++ app?
Both apps running on the same machine.

Seems that you could get windows handles, use the clipboard (?), or
maybe even sockets. But I was wondering if there is anything more
elegant or direct.

What are others doing to solve this?

 

[Lucian Wischik]

I'm not the O.P., but I have a related question: What is the usual way
of communicating between a C# app and an unmanaged C++ app?
Both apps running on the same machine.
Seems that you could get windows handles, use the clipboard (?), or
maybe even sockets. But I was wondering if there is anything more
elegant or direct.
What are others doing to solve this?

Or pipes, windows messages, disk files. I also like sending XML over
TCP, even on the same machine.

But really, if the communication is more than can be handled by just a
simple pipe (e.g. "process1 > process2" at the command-line) then I'm
quite suspicious of it. Good candidates for merging the two apps into
a single combined C#+CLI app. I mean, we spend so much effort
(pickling, RPC, proxies) to make it look as though two remote apps are
really part of the same single app, that's if we have the chance to
make two apps *really* part of the same single app then we should use
it!