How can i associate a process with my own application process VB.NET

Question

3.00/5 (2 votes)

See more:

Hi everyone,

To cut the long story short, i am implementing an application that runs another application during a click of a button using Diagnostics.Process.Start() function and also monitor the process of that application. Now my problem is this, i want to know how i can associate the process of the application i started usint Diagnostics.Process.Start() with the process of my .NET application so what whenever my .NET application closes, the process of the application i ran will also close.

I don't want to handle this in the Form1.FormClosing Event. The reason for this is because there might be some malcious users that might go straight into the taskbar manager and terminate the process of my .NET application and leaving the process of the application i ran active thereby removing the monitoring i coded inside my .NET application.

Pls i need help on this, i want to know how i can associate the process of my .NET application and the third party application i ran using Diagnostics.Process.Start() so that whenever my .NET application shuts down, the third party application will also shut down.

Thanks in advance!

Posted 25-Aug-13 10:26am

Joeadeoye

Add a Solution

2 solutions

Solution 1

[EDIT]~~There is no such thing as association between processes.~~ Processes can be indirectly associated using the job objects, please see Solution 2. At the same time, you can take care about your child processes by yourself. [END EDIT]

First of all, note that Process.Start returns you the instance of the external process started. You can use this instance to kill the process: http://msdn.microsoft.com/en-us/library/system.diagnostics.process.kill.aspx[^].

To do the opposite, to trigger something when the external process is exited, you can use Process.WaitForExit methods:
http://msdn.microsoft.com/en-us/library/fb4aw7b8.aspx[^],
http://msdn.microsoft.com/en-us/library/ty0d8k56.aspx[^].

As this call is blocking, in most cases, a separate thread is required to wait.

—SA

Posted 25-Aug-13 10:36am

Sergey Alexandrovich Kryukov

Updated 25-Aug-13 11:35am

v2

Comments

Zoltán Zörgő 25-Aug-13 16:59pm

I thought the same, but it looks that there is such thing as association between processes. Look what I have found.

I credited your solutions and fixed my statement.

Thank you very much.
—SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Accepted Answer · 2013-08-25T10:57:00

It look that there is a solution to your request. Look here: http://stackoverflow.com/questions/3342941/kill-child-process-when-parent-process-is-killed#answer-4657392[^]. The code is built around the Job Object tool[^]:

Quote:
A job object allows groups of processes to be managed as a unit. Job objects are namable, securable, sharable objects that control attributes of the processes associated with them. Operations performed on a job object affect all processes associated with the job object. Examples include enforcing limits such as working set size and process priority or terminating all processes associated with a job.