Application. Exit Событие

Определение

Происходит непосредственно перед завершением работы приложения и его отменой. Occurs just before an application shuts down and cannot be canceled.

Тип события

Примеры

В следующем примере показано, как: The following example demonstrates how to:

Обработайте Exit событие. Handle the Exit event.

Проверьте и обновите ApplicationExitCode свойство объекта ExitEventArgs . Inspect and update the ApplicationExitCode property of the ExitEventArgs.

Запись записи в журнал приложения в изолированном хранилище. Write an entry to an application log in isolated storage.

Сохранение состояния приложения в изолированном хранилище. Persist the application state to isolated storage.

Комментарии

Приложение может завершить работу по одной из следующих причин: An application can shut down for either of the following reasons:

ShutdownМетод Application объекта вызывается либо явным образом, либо в соответствии со ShutdownMode свойством. The Shutdown method of the Application object is called, either explicitly or as determined by the ShutdownMode property.

Пользователь завершает сеанс путем выхода из системы или завершения его работы. The user ends the session by logging off or shutting down.

Можно определить, когда происходит завершение работы приложения, обрабатывая Exit событие, и при необходимости выполнить дополнительную обработку. You can detect when application shutdown occurs by handling the Exit event, and perform any additional processing as required.

Кроме того, можно выполнять Exit проверку или изменение кода выхода приложения, если вам не нужно вызывать его Shutdown явным образом. You can also handle Exit to inspect or change the application exit code when you don’t need to call Shutdown explicitly. Код выхода предоставляется из ApplicationExitCode свойства ExitEventArgs аргумента, который передается в Exit обработчик событий. The exit code is exposed from the ApplicationExitCode property of the ExitEventArgs argument that’s passed to the Exit event handler. При остановке работы приложения код выхода передается в операционную систему для последующей обработки. When the application stops running, the exit code is passed to the operating system for subsequent processing.

Если приложение обрабатывает событие, SessionEnding а затем отменяет его, Exit не вызывается и приложение продолжит выполнение в соответствии с режимом завершения работы. If your application handles the SessionEnding event and subsequently cancels it, Exit is not raised and the application continues running in accordance with the shutdown mode.

Код выхода можно задать из приложения браузера XAML (XBAP), хотя значение игнорируется. The exit code can be set from an XAML browser application (XBAP), although the value is ignored.

Для XBAP Exit вызывается в следующих случаях: For XBAPs, Exit is raised in the following circumstances:

Выполняется переход к XBAP из. An XBAP is navigated away from.

В Internet Explorer 7, когда вкладка, на которой размещается XBAP, закрыта. In Internet Explorer 7, when the tab that is hosting the XBAP is closed.

Закрывается браузер. When the browser is closed.

Во всех случаях значение ApplicationExitCode свойства игнорируется. In all cases, the value of the ApplicationExitCode property is ignored.

Application. Application Exit Событие

Определение

Происходит при закрытии приложения. Occurs when the application is about to shut down.

Тип события

Примеры

В следующем примере кода показаны две формы и выход из приложения при закрытии обеих форм. The following code example displays two forms and exits the application when both forms are closed. Когда приложение запускается и завершает работу, сохраняется расположение каждой формы. When the application starts and exits, the position of each form is remembered. В этом примере показано использование ApplicationExit события для получения сведений о том, когда следует сохранять положение формы в файле и когда FileStream должно быть закрыто. This example demonstrates using the ApplicationExit event to know when the form positions should be persisted to the file, and when the FileStream should be closed.

Класс MyApplicationContext наследует от ApplicationContext и отслеживает, когда закрывается каждая форма, и завершает текущий поток, когда они оба. The class MyApplicationContext inherits from ApplicationContext and keeps track of when each form is closed, and exits the current thread when they both are. Класс запоминает расположение каждой формы при его закрытии. The class remembers the position of each form when it is closed. Когда ApplicationExit происходит событие, класс записывает позиции каждого пользователя в файл. When the ApplicationExit event occurs, the class writes the positions of each for the user to the file. Данные о положении формы хранятся в файле appdata.txt , созданном в расположении, определенном параметром UserAppDataPath . The form position data is stored in a file titled appdata.txt that is created in the location determined by UserAppDataPath. Main Метод вызывает, Application.Run(context) чтобы запустить приложение, используя ApplicationContext . The Main method calls Application.Run(context) to start the application given the ApplicationContext.

Этот код является выдержкой из примера, показанного в ApplicationContext обзоре класса. This code is an excerpt from the example shown in the ApplicationContext class overview. ApplicationContextПолный листинг кода см. в разделе. See ApplicationContext for the whole code listing.

Комментарии

Необходимо присоединить обработчики событий к ApplicationExit событию для выполнения необработанных, обязательных задач, прежде чем приложение прекратит работу. You must attach the event handlers to the ApplicationExit event to perform unhandled, required tasks before the application stops running. Можно закрыть файлы, открытые этим приложением, или удалить объекты, которые не были освобождены при сборке мусора. You can close files opened by this application, or dispose of objects that garbage collection did not reclaim.

Поскольку это статическое событие, необходимо отсоединить все обработчики событий, присоединенные к этому событию, в ApplicationExit самом обработчике событий. Because this is a static event, you must detach any event handlers attached to this event in the ApplicationExit event handler itself. Если вы не отсоединяете эти обработчики, они остаются прикрепленными к событию и продолжают потреблять память. If you do not detach these handlers, they will remain attached to the event and continue to consume memory.

Application. Exit Method

Definition

Informs all message pumps that they must terminate, and then closes all application windows after the messages have been processed.

Overloads

Informs all message pumps that they must terminate, and then closes all application windows after the messages have been processed.

Informs all message pumps that they must terminate, and then closes all application windows after the messages have been processed.

Informs all message pumps that they must terminate, and then closes all application windows after the messages have been processed.

Examples

The following code example lists numbers in a list box on a form. Each time you click button1 , the application adds another number to the list.

The Main method calls Run to start the application, which creates the form, listBox1 , and button1 . When the user clicks button1 , the button1_Click method adds numbers one to three to the list box, and displays a MessageBox. If the user clicks No on the MessageBox, the button1_Click method adds another number to the list. If the user clicks Yes, the application calls Exit, to process all remaining messages in the queue and then to quit.

The example requires that listBox1 and button1 have been instantiated and placed on a form.

Remarks

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. To exit a message loop for the current thread only, call ExitThread.

Exit raises the following events and performs the associated conditional actions:

A FormClosing event is raised for every form represented by the OpenForms property. This event can be canceled by setting the Cancel property of their FormClosingEventArgs parameter to true .

If one of more of the handlers cancels the event, then Exit returns without further action. Otherwise, a FormClosed event is raised for every open form, then all running message loops and forms are closed.

The Exit method does not raise the Closed and Closing events, which are obsolete as of .NET Framework 2.0.

Application. Application Exit Event

Definition

Occurs when the application is about to shut down.

Event Type

Examples

The following code example displays two forms and exits the application when both forms are closed. When the application starts and exits, the position of each form is remembered. This example demonstrates using the ApplicationExit event to know when the form positions should be persisted to the file, and when the FileStream should be closed.

The class MyApplicationContext inherits from ApplicationContext and keeps track of when each form is closed, and exits the current thread when they both are. The class remembers the position of each form when it is closed. When the ApplicationExit event occurs, the class writes the positions of each for the user to the file. The form position data is stored in a file titled appdata.txt that is created in the location determined by UserAppDataPath. The Main method calls Application.Run(context) to start the application given the ApplicationContext.

This code is an excerpt from the example shown in the ApplicationContext class overview. See ApplicationContext for the whole code listing.

Remarks

You must attach the event handlers to the ApplicationExit event to perform unhandled, required tasks before the application stops running. You can close files opened by this application, or dispose of objects that garbage collection did not reclaim.

Because this is a static event, you must detach any event handlers attached to this event in the ApplicationExit event handler itself. If you do not detach these handlers, they will remain attached to the event and continue to consume memory.

How to properly exit a C# application?

I have a published application in C#. The problem here is whenever I close the main form by clicking on the red exit button, it closes the form but it doesn’t close the application. I found this out when I tried shutting down the computer, hopeful that the application I made was running smoothly then I was bombarded by a lot of child windows with which I have put MessageBox Alerts.

I tried Application.Exit but it still calls all the child windows and alerts and I don’t know how to use Environment.Exit and which integer to put into it.

By the way, whenever my forms call the formclosed or form closing event I close the application with a this.Hide() function; Does that affect how my application is behaving now?

9 Answers 9

Informs all message pumps that they must terminate, and then closes all application windows after the messages have been processed. This is the code to use if you are have called Application.Run (WinForms applications), this method stops all running message loops on all threads and closes all windows of the application.

Terminates this process and gives the underlying operating system the specified exit code. This is the code to call when you are using console application.

This article, Application.Exit vs. Environment.Exit, points towards a good tip:

You can determine if System.Windows.Forms.Application.Run has been called by checking the System.Windows.Forms.Application.MessageLoop property. If true, then Run has been called and you can assume that a WinForms application is executing as follows.

I know this is not the problem you had, however another reason this could happen is you have a non background thread open in your application.

When IsBackground is false it will keep your program open till the thread completes, if you set IsBackground to true the thread will not keep the program open. Things like BackgroundWoker , ThreadPool , and Task all internally use a thread with IsBackground set to true .

All you need is System.Environment.Exit(1);

And it uses the system namespace «using System» that’s pretty much always there when you start a project.

I would either one of the following:

for a winform or

for a console application (works on winforms too).

By the way. whenever my forms call the formclosed or form closing event I close the applciation with a this.Hide() function. Does that affect how my application is behaving now?

In short, yes. The entire application will end when the main form (the form started via Application.Run in the Main method) is closed (not hidden).

If your entire application should always fully terminate whenever your main form is closed then you should just remove that form closed handler. By not canceling that event and just letting them form close when the user closes it you will get your desired behavior. As for all of the other forms, if you don’t intend to show that same instance of the form again you just just let them close, rather than preventing closure and hiding them. If you are showing them again, then hiding them may be fine.

If you want to be able to have the user click the «x» for your main form, but have another form stay open and, in effect, become the «new» main form, then it’s a bit more complicated. In such a case you will need to just hide your main form rather than closing it, but you’ll need to add in some sort of mechanism that will actually close the main form when you really do want your app to end. If this is the situation that you’re in then you’ll need to add more details to your question describing what types of applications should and should not actually end the program.