C# persistent process after closing app

Question

0.00/5 (No votes)

See more:

Hi,
I'm bulding a c# application who make some operation and start one or more external application
with

C#

string pathMyApp = ......external executable
ProcessStartInfo startInfo = new ProcessStartInfo() { FileName = "pathMyApp", Arguments = ......someAppParameter, };
proc = new Process() { StartInfo = startInfo, };
proc.Start()

It's all Ok but after external process start the main app continue to end and when it finish all process ends too.

Is it possible to close my mainApp and continue executing of child app?

Now i've putted a readkey at the end of main application to prevent the end but it's not good.
have any solution?
thank's

What I have tried:

C#

I've tried with
<pre lang="C#">ThreadStart ths = new ThreadStart(() =&gt; proc.Start());
           Thread th = new Thread(ths);
           th.Start();</pre>

too, but is the same.

Posted 6-Oct-16 5:50am

maurodefilippis

Updated 6-Oct-16 6:56am

Add a Solution

Comments

Rob Philpott 6-Oct-16 12:05pm

This has me confused. What you describe doesn't match what I understood happens, and indeed when I write a simple console app which launches Notepad, Notepad stays when the console app dies.

The processes you are trying to start, what are they? Console/Windows/Services?

[no name] 6-Oct-16 12:06pm

Haven't tested it but you might try UseShellExecute = true

1 solution

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)

OriginalGriff · Answer 1 · 2016-10-06T06:56:00

Processes and Threads are different in one important respect: when your application closes, all it's thread are closed as well provided they are marked as "background" - if they aren't, then they persist even once the app itself is closed. The only way to override that is to call Environment.Exit instead of Application.Exit, as that terminates all running threads associated with the app regardless of their background status.
Processes always survive the application - they are independant of the app and are not terminated automatically.

I suspect you need to look at your code again, as I dont; think it operates teh way you think it is!