Home/ Questions/Q 6074227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T10:21:31+00:00

We have a solution written by an outside contractor whereby a .net Windows Service

  • 0

We have a solution written by an outside contractor whereby a .net Windows Service runs continually, monitoring the system time, and, during the night, when there is very little activity, executes a long task, signals when the task has completed, then returns to monitoring the time until the next night.

There is currently no way to monitor or query the status of the process being run by the service, though we can query the service itself to see whether it is being run by Windows, or not.

In the event of a failure, the contractor provided us with a separate executable which can also run the same task.

The problem is, there is no way to know whether the service is currently executing the long task, and it is simply incomplete, or whether it has entered some kind of failure state, meaning that the standalone executable might easily be run in error, because the service is still processing the task.

Ultimately I would like to be able to send queries to the service, find out its state, and give it instructions while it is running.

What method should I use to start sending and receiving these messages?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are several methods of Inter-process communication available to you, the most obvious choices that spring to mind are Named Pipes or Sockets.

    Either of those would work fine, however rather than trying to implement these directly I would instead recommend that you host a WCF Service (inside the Windows service) and use this for interprocess communication.

    WCF Services can be seamlessly configured to use either Sockets or Named Pipes (as well as a range of less suitable options) as the underlying transport mechanism, as well as simplifying the development of IPC (Inter Process Communication) systems.

    There is a wealth of information on WCF Services and how to implement a WCF Service on the web – just try Google.

    (If for some reason you are using .Net 2.0 instead of .Net 3.5 or above then you should instead look at .Net Remoting – it is essentially the predecessor to WCF and works in a completely different way, however basically achieves the same thing).

    • 0