Stop Debugging Event in C#

Question

How or where can I run a command when the application closes, even if is a debug stop?

I need to perform a command in any exit, even if the user is a developer and click on "stop debugging" button on Visual Studio.

I try with

Application.ApplicationExit += new EventHandler(this.OnApplicationExit);

but it doesn't work. Maybe I'm wrong or is not the event.

I'm using Winforms and not, on Form Close can't be the event.

I'm using Visual Studio 2005 Net Framework 2.0 (by client requirement), but is just for information.

Maybe can I rewrite this?:

public static void Exit();

I'm curious - why would the client be bothered about debug being stopped? — m.edmondson, Jun 13 '12 at 22:06
@m.edmondson I was looking at doing this for some web testing - it needs to fire up browsers during tests and exiting the debugger doesnt run the rest of a using block that cleans up. This is a bit annoying as you end up with lots of browsers being open — JonnyRaa, Jan 27 '14 at 10:33

score 15 · Accepted Answer · edited Dec 17 '16 at 17:30

15

The problem is the "stop debugging" function will halt the application entirely - so no more code within that application will run.

Your only way of achieving this would be to watch the process being debugged externally and execute the code if it has been halted.

According to [MSDN]:

Stop Debugging terminates the process you are debugging if the program was launched from Visual Studio.

However you may be able to achieve what you want with a visual studio add-in.

edited Dec 17 '16 at 17:30

Jacob

3,598
4
35
56

answered Jun 13 '12 at 22:02

m.edmondson

30,382
27
123
206

I understand. +1 for the workaround. Do you have any link to read about that can be done in the app itself, to include it on the TD/FD app documentation? Thanks. – Leandro Bardelli Jun 13 '12 at 22:03
Unfortunately not as I've never done anything like this before - perhaps another answer will come along. – m.edmondson Jun 13 '12 at 22:05
What does it mean to "halt the application entirely"? Sending WM_CLOSE to the main form? Or calling TerminateProcess? You suggest the latter is what happens, but do you have any evidence to support this claim? – kol Jun 13 '12 at 22:06
I have no evidence either way - perhaps you could improve my answer? – m.edmondson Jun 13 '12 at 22:07
@m.edmondson Unfortunately not... I'm just also curious about what the "stop debugging" button does :) – kol Jun 13 '12 at 22:11
1

@kol - I've done a quick google and added to my answer - looks like it terminates the process – m.edmondson Jun 13 '12 at 22:13
it seems to be the final answer. But I keep the workaround, is not a bad idea for all. – Leandro Bardelli Jun 13 '12 at 22:17
1

@Leandro - I've updated my answer, you may be able to achieve this with an add-in – m.edmondson Jun 13 '12 at 22:20
Yep I want to try if Process_Exit works but I can't get solve it. I need to call a control and not a messagebox – Leandro Bardelli Jun 13 '12 at 22:26
Process_Exit doesn't work. It's event handler doesn't run either. – Triynko Nov 24 '15 at 12:54

score 1 · Answer 2 · answered Jun 13 '12 at 22:08

1

According to MSDN: http://msdn.microsoft.com/en-us/library/system.windows.forms.application.applicationexit%28v=vs.80%29.aspx

// Handle the ApplicationExit event to know when the application is exiting.
Application.ApplicationExit += new EventHandler(this.OnApplicationExit);

private void OnApplicationExit(object sender, EventArgs e) {
// When the application is exiting
}

Is this what you implemented?

answered Jun 13 '12 at 22:08

Mausimo

8,018
12
52
70

I don't think this will execute when halting the debug? – m.edmondson Jun 13 '12 at 22:10
Yep, that was I tried. But it doesnt work (works only with the normal flow of the app). – Leandro Bardelli Jun 13 '12 at 22:12
1

Oops, I miss-read the question. He wants it to run even if the program is stopped by a debug point by a developer. I do not believe it will execute when using debug. – Mausimo Jun 13 '12 at 22:12
np, your comment helps me on my question – Leandro Bardelli Jun 13 '12 at 22:15

score 0 · Answer 3 · answered Jul 26 '21 at 15:53

0

You can use use Suspend and Resume layout. Also, if you have a combo box filled with stuff, it can slow you down. I would also consider going under "Solution Explorer" and right click and select "Properties" at the bottom. Choose "Configuration Properties" and select "Release" verse "Debugging." This will greatly improve form loading time. This link will explain

answered Jul 26 '21 at 15:53

Justin Linwood Ross

1
2

1

Welcome to S.O. Please avoid use links to answer in S.O. Please read the guidelines. – Leandro Bardelli Jul 26 '21 at 19:17

score -1 · Answer 4 · edited May 23 '17 at 12:16

-1

Try this:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Windows.Forms;

namespace Prueba {
    static class Program {
        [STAThread]
        static void Main() {
            Application.EnableVisualStyles();
            Application.SetCompatibleTextRenderingDefault(false);
            Application.Run(new Form1());
            //This is the magic line code :P
            AppDomain.CurrentDomain.ProcessExit += new EventHandler(CurrentDomain_ProcessExit);
        }

        static void CurrentDomain_ProcessExit(object sender, EventArgs e) {
            MessageBox.Show("");
        }
    }
}

The reference is here (Fredrik Mörk): .NET Console Application Exit Event

edited May 23 '17 at 12:16

Community

1
1

answered Jun 13 '12 at 22:16

batressc

1,499
1
18
28

How can I call from CurrentDomain_ProcessExit a control on my Form1 ? – Leandro Bardelli Jun 13 '12 at 22:22
Want to launch a form from this event? – batressc Jun 13 '12 at 22:27
I need to change a lot of things, and one of them is a dispose of an object (notifyicon) on Form1 (created by designer) – Leandro Bardelli Jun 13 '12 at 22:29
If you need change any propertie of an object before to luch a form, in the constructor of the form, after of the method InitializeComponents(), you can write the necesary code for changing the properties of the objects. Explain me more what you do. – batressc Jun 13 '12 at 22:42
dispose the notifyicon or run a public void that dispose it when the app stops (also close a stream, etc etc etc). Clean up the solution and the build – Leandro Bardelli Jun 13 '12 at 22:46
Personally I think you should not close streams or dispose objects at this level of the program, each object must be dispose, in this case, to close the form ... but if you need to do this, you have to declare a static class and declare static variables (globals at application), if you need to force the release or closing streams, then put the code in that method. (Sorry my english, i can't speak english) – batressc Jun 14 '12 at 14:22
this doesnt seem to work for me. I am trying from a console app. – JonnyRaa Jan 27 '14 at 10:45
16

This absolutely does not work. The Process_Exit handler is not called when I press the stop debugging button. – Triynko Nov 24 '15 at 12:52

Stop Debugging Event in C#

4 Answers4

Linked