First a bit of background: I have a WPF application, which is a GUI-front-end to a legacy Win32-application. The legacy app runs as DLL in a separate thread. The commands the user chooses in the UI are invoked on that “legacy thread”.
If the “legacy thread” finishes, the GUI-front-end cannot do anything useful anymore, so I need to shutdown the WPF-application. Therefore, at the end of the thread’s method, I call Application.Current.Shutdown().
Since I am not on the main thread, I need to invoke this command. However, then I noticed that the Dispatcher also has BeginInvokeShutdown() to shutdown the dispatcher. So my question is: What is the difference between invoking
Application.Current.Shutdown();
and calling
Application.Current.Dispatcher.BeginInvokeShutdown();
I did some more testing, and now I think I know the differences:
1) As stated in the MSDN page,
BeginInvokeShutdown, besides shutting down the Dispatcher, also clears/aborts its queue.Shutdownfirst handles all items in the Dispatcher queue.2) In an application I can handle the Application.Exit event. This event is fired when I call Shutdown, but NOT fired when I call BeginInvokeShutdown! The same applies to Window.Closing and Window.Closed.
As for similarities, in both cases the main thread is exited. Depending on other running threads, this also shuts down the process: non-background threads are run to completion before the process exits.
Below is my test code. Comment one or the other method call in Application_Startup: