Interapplication comunication

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Nikolay Petrov
    #1

    Interapplication comunication

    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?

    Tags: None
    • Charles Law
      #2
      Re: Interapplicatio n comunication

      Hi Nikolay

      There are API functions DebugActiveProc ess, WaitForDebugEve nt and others
      that you can use to attach to a running process and receive debug output.

      HTH

      Charles


      "Nikolay Petrov" <johntup2@mail. bg> wrote in message
      news:1127216265 .312331.113570@ g47g2000cwa.goo glegroups.com.. .[color=blue]
      > 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?
      >[/color]


        Comment

        • alantolan@users.com
          #3
          Re: Interapplicatio n comunication


          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.

            Comment

            Previous template Next
            Working...