Interapplication comunication

  • Thread starter Thread starter Nikolay Petrov
  • Start date Start date
N

Nikolay Petrov

Hi,
I need to acheive something, but I am not sure which technology should
I use. My best guess is Remoting, followed by Sockets.

Here is what I want to achieve.
Every one uses the Debug.Write/WriteLine. It is very handy.
I would like to mimic this functionality. Let's say I have some app, or
bunch of apps running on a machine. I want to start other app, let's
call it "Monitor", which should receive notifications from the others
and display them to the user.

The apps, which should generate the information must be capable to find
out if the Monitor app is running, and fetch the information to it. The
code for this shouldn't be CPU consuming.

Any ideas?
 
Hi Nikolay

There are API functions DebugActiveProcess, WaitForDebugEvent and others
that you can use to attach to a running process and receive debug output.

HTH

Charles
 
Have a look at the Trace functions and the TraceListeners.

1) By default Trace functionality is available in both debug and
release versions of the code but Debug doesn't work in the release
version.

2) By modifying the App.Config file one can add a Trace listener at
runtime to display the messages produced by Trace

3) There are 5 levels of (4 and off) Trace messages to allow one to
filter the messages displayed - this can be configured at runtime.


hth,
Alan.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top