How to get Task manager process closing events in c#?

Question

How to get Task manager process closing events in c#?

Sachwet 1

Hi Team
I am Implimenting a server(APIGatewat.exe which is console exe) to launch other console exe(act as other servers) in background without
user intercation mode
i am able to launch the exe(using process start) but when im closing my Main exe in background (like if exe get close in task manager or if it get close by other UI tool)
my other exe are not getting close when i use the cross mark in corner to close other exe also gets close for this im using event

            AppDomain.CurrentDomain.ProcessExit += new EventHandler(ProcessExitHandler);

anyone have idea how we can handle taskmanager process cloing events? or any other solution

RLWA32 49,636 Reputation points

2024-01-16T09:03:29.66+00:00

For what its worth the Windows API mechanism to accomplish your objective is to use a Job Object. You can read more about this at Destroying all child processes (and grandchildren) when the parent exits.
Sachwet 1 Reputation point

2024-01-16T13:47:03.0666667+00:00

@RLWA32 Thank you for your prompt reply ..How to use it in C# without exporting external DLL?
RLWA32 49,636 Reputation points

2024-01-16T14:00:06.18+00:00

How to use it in C# without exporting external DLL?

I'm not aware of any native, Microsoft supplied .Net support for Job Objects. So you would have to use P/invoke with the Windows APIs or find a third-party package.

Mahesh Deshmane 0

If you need to handle the scenario where the main process is forcefully terminated, and you want to ensure that the child processes are also terminated, you can consider the following approach:

Create a Parent-Child Relationship: When you start the child processes from the main process, establish a parent-child relationship using the Process class.
Handle Closing Events: Handle both AppDomain.CurrentDomain.ProcessExit and Console.CancelKeyPress events to ensure that you can clean up resources and terminate child processes gracefully. Here's an example demonstrating this:

using System;
using System.Diagnostics;
using System.Threading;

class Program
{
    static void Main()
    {
        Console.CancelKeyPress += (sender, eventArgs) =>
        {
            Console.WriteLine("Ctrl+C detected. Cleaning up...");
            // Add cleanup logic if needed
            TerminateChildProcesses();
        };

        AppDomain.CurrentDomain.ProcessExit += (sender, eventArgs) =>
        {
            Console.WriteLine("Process exit detected. Cleaning up...");
            // Add cleanup logic if needed
            TerminateChildProcesses();
        };

        // Start child processes
        StartChildProcesses();

        Console.WriteLine("Press Ctrl+C to exit.");

        // Keep the main process alive
        Thread.Sleep(Timeout.Infinite);
    }

    static void StartChildProcesses()
    {
        // Your code to start child processes
        // Example:
        var childProcess = new Process
        {
            StartInfo = new ProcessStartInfo
            {
                FileName = "ChildProcess.exe",
                UseShellExecute = false,
                RedirectStandardOutput = true,
                CreateNoWindow = true
            }
        };

        childProcess.Start();
    }

    static void TerminateChildProcesses()
    {
        // Your code to terminate child processes gracefully
        // Example:
        // Kill the child processes
        foreach (var process in Process.GetProcessesByName("ChildProcess"))
        {
            process.Kill();
        }
    }
}

In this example, the StartChildProcesses method is where you initiate the child processes, and the TerminateChildProcesses method is where you terminate them when the main process receives termination signals. Make sure to replace "ChildProcess.exe" with the actual names of your child processes. This approach should help handle the termination of child processes when the main process is forcefully terminated.

Sachwet 1 Reputation point

2024-01-23T04:39:53.8233333+00:00

Hi @Mahesh Deshmane Thank you for your reply and same thing above i have implemented but my Parent process is getting closed my React UI tool so that closing event i am unable to detect and handle .
RLWA32 49,636 Reputation points

2024-01-23T08:42:19.84+00:00

@Sachwet The Windows APIs to use job objects are implemented in the system's kernel32.dll which is loaded into your process whether you use Job Objects or not. So its not an "external dll". The following demonstrates a .Net Framework console application creating several child processes ( 4 instances of a console application without windows and 4 instances of notepad with hidden windows). All are terminated when the parent process is closed by Task Manager, pressing the "X" in the parent application console window or responding to the parent console orderly close input.

Once the child process is created in the job object the parent process does not need to track it by its name or by its process id. The system does all the work for you.
Sachwet 1 Reputation point

2024-01-30T05:43:14.34+00:00

Hi @RLWA32 Thank you for the reply, actually my console exe which is launching from electron app, so it being handled from electron app that when its getting close it is closing its child exe as well childs entire process tree this way we handled it now.

Your answer

RLWA32 49,636 Reputation points

2024-01-16T09:03:29.66+00:00

For what its worth the Windows API mechanism to accomplish your objective is to use a Job Object. You can read more about this at Destroying all child processes (and grandchildren) when the parent exits.
Sachwet 1 Reputation point

2024-01-16T13:47:03.0666667+00:00

@RLWA32 Thank you for your prompt reply ..How to use it in C# without exporting external DLL?
RLWA32 49,636 Reputation points

2024-01-16T14:00:06.18+00:00

How to use it in C# without exporting external DLL?

I'm not aware of any native, Microsoft supplied .Net support for Job Objects. So you would have to use P/invoke with the Windows APIs or find a third-party package.
Sachwet 1 Reputation point

2024-01-23T04:39:53.8233333+00:00

Hi @Mahesh Deshmane Thank you for your reply and same thing above i have implemented but my Parent process is getting closed my React UI tool so that closing event i am unable to detect and handle .
RLWA32 49,636 Reputation points

2024-01-23T08:42:19.84+00:00

@Sachwet The Windows APIs to use job objects are implemented in the system's kernel32.dll which is loaded into your process whether you use Job Objects or not. So its not an "external dll". The following demonstrates a .Net Framework console application creating several child processes ( 4 instances of a console application without windows and 4 instances of notepad with hidden windows). All are terminated when the parent process is closed by Task Manager, pressing the "X" in the parent application console window or responding to the parent console orderly close input.

Once the child process is created in the job object the parent process does not need to track it by its name or by its process id. The system does all the work for you.
Sachwet 1 Reputation point

2024-01-30T05:43:14.34+00:00

Hi @RLWA32 Thank you for the reply, actually my console exe which is launching from electron app, so it being handled from electron app that when its getting close it is closing its child exe as well childs entire process tree this way we handled it now.

Share via

How to get Task manager process closing events in c#?

Your answer