You can use .NET's Process Class to start a process as other people described. Then the question is when to call.
In most cases, using either Form.Closing
or Form.Closed
event seems to be an easy choice.
However, if someone else can handle the event and can set CancelEvnetArgs.Cancel
to true, this may not be the right place to do this. Also, Form.Closing
and Form.Closed
events will not be raised when Application.Exit()
is called. I am not sure whether either of events will be raised if any unhandled exceptions occur. (Also, you have to decide whether you want to launch the second application in case of Application.Exit()
or any unhandled exception).
If you really want to make sure the second application (App2) launches after the first application (App1) exited, you can play a trick:
- Create a separate application (App0)
- App0 launches App1
- App0 waits for App1 to exit with Process.WaitExit()
- App0 launches App2 and exits itself
The sample console app attached below shows a very simple case: my sample app launches the notepad first. Then, when the notepad exits, it launches mspaint and exits itself.
If you want to hide the console, you can simply set the 'Output Type' property from 'Console Application' to 'Windows Application' under 'Application' tab of Project Property.
Sample code:
using System;
using System.Diagnostics;
namespace ProcessExitSample
{
class Program
{
static void Main(string[] args)
{
try
{
Process firstProc = new Process();
firstProc.StartInfo.FileName = "notepad.exe";
firstProc.EnableRaisingEvents = true;
firstProc.Start();
firstProc.WaitForExit();
//You may want to perform different actions depending on the exit code.
Console.WriteLine("First process exited: " + firstProc.ExitCode);
Process secondProc = new Process();
secondProc.StartInfo.FileName = "mspaint.exe";
secondProc.Start();
}
catch (Exception ex)
{
Console.WriteLine("An error occurred!!!: " + ex.Message);
return;
}
}
}
}