17

I have an application that imports data from Excel. However, when I run the winforms app and I intrupt the application, using System.Windows.Forms.Application.Exit(); I can still see the "MyAppName".vshost32.exe running in task manager.

When I exit the application in debug mode, the form closes, but the VS IDE is not "stopped".

How do I ensure the application ends correctly.

Troy
  • 1,659
  • 4
  • 19
  • 33
  • Similar question to http://stackoverflow.com/questions/4314436/i-cant-kill-myapp-vshost-exe – dash Dec 14 '11 at 16:29

4 Answers4

24

Your call to Application.Exit() is working fine. The MyAppName.vshost32.exe executable is a host for debugging purposes. It runs whilst you have a project open in Visual Studio, regardless of if there is an active debugging session.

Update: Ok, I misunderstood. The above is true, but you're probably having problems with hung threads in the background. You need to terminate your threads to make it close properly. Asher's answer covers this. If you're just trying to do a super-hacky quick-and-dirty kill, you can use the following (though I take no responsibility for side effects, since it's extremely hacky):

System.Diagnostics.Process.GetCurrentProcess().Kill();

Polynomial
  • 27,674
  • 12
  • 80
  • 107
  • 1
    I agree in general, except that in this specific scenario the VS debugger session is still going, indicating that the app is still running (at least, that's how I interpreted the question) – Cameron Dec 14 '11 at 16:31
  • Polynomial the syntax should be System.Diagnostics.Process.GetCurrentProcess().Kill(); – Nick Binnet Jun 22 '13 at 19:17
17

The process doesn't terminate because it still has foreground threads running.

If you create threads in your application you need to mark them as background threads or make sure they terminate when you want the application to exit.

Asher
  • 1,867
  • 15
  • 24
7

Have you tried the more brutal Environment.Exit() function?

Application.Exit() just sends a message saying to shutdown; if the message never gets processed (for whatever reason), the application will stay running indefinitely.

From the MSDN documentation of Application.Exit():

The Exit method stops all running message loops on all threads and closes all windows of the application. This method does not necessarily force the application to exit. The Exit method is typically called from within a message loop, and forces Run to return.

Cameron
  • 96,106
  • 25
  • 196
  • 225
  • Well, the form exits, and when I do a breakpoint, I do hit that line, and it executes fine. So that line does get executed. – Troy Dec 14 '11 at 16:32
  • @Troy: Right, but calling `Application.Exit()` just posts a message to the queue of all the message pumps; your form's pump seems to process the message and exit, but there's something else (another thread, maybe?) that isn't heeding the request – Cameron Dec 14 '11 at 16:38
4

I had a similar problem caused by a third party tool that did not allow me to set the threads as Background. Polynomial had the right idea, but then syntax is like this:

System.Diagnostics.Process.GetCurrentProcess().Kill();
Jacob Raines
  • 116
  • 4