By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,515 Members | 1,061 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,515 IT Pros & Developers. It's quick & easy.

Interapplication comunication

P: n/a
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?

Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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
"Nikolay Petrov" <jo******@mail.bg> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
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?

Nov 21 '05 #2

P: n/a

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.

Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.