How to Pause and Resume in Threading?

Question

5.00/5 (1 vote)

See more:

, +

I know Thread.Suspend() and Thread.Resume() is not good one for program practice.

I have built one small windows form application.
When user close the Window Form while processing the task, i'm showing warning message box(FormClosing Event). If user clicks "yes" button then it will Exit the application. If they click "No" then it will perform the action.

Even though warning Message Box appears, application performing the task. But i want if the warning message box appears then i must pause the thread. If user clicked "yes" button then i'll terminate. If user clicked "No" then i'll continue the process.

Please guide me on this. . . ,

C#

private void frmTranxitCCTVJobCreation_FormClosing(object sender, FormClosingEventArgs e)
        {
            if (e.CloseReason == CloseReason.UserClosing)
            {
                if (bIsButtonClicked == true)
                {
                    if (_threadProcessCCTV.IsAlive)
                    {
                        dynamic mboxResult = MessageBox.Show("Are you sure you want to exit the form?", "Tranxit CCTV Job Creation Tool", MessageBoxButtons.YesNo);
                        if (mboxResult == DialogResult.Yes)
                        {
                            //e.Cancel = false;
                            Application.Exit();
                        }

                        if (mboxResult == DialogResult.No)
                        {
                            // Cancel the Closing event from closing the form.
                            e.Cancel = true;
                        }
                    }
                }
            }
        }

Posted 23-Dec-13 20:53pm

mn.sathish

Updated 28-Dec-13 23:32pm

agent_kruger

v4

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-12-23T21:03:00

It's good that you understand that thread Pause and Resume are bad. They are really and critically dangerous, so those methods have been deprecated in .NET. The right approach is: you need to pause and resume the thread operation only in some selected point of its code, where the thread makes a blocking call. Such call puts the thread in a special wait state, wasting no CPU time; the thread is switched off and not scheduled back to execution until it is waken up by some condition.

If your purpose is just pausing and resuming a thread from some other thread use to "throttle" your thread's execution, the adequate class is the event wait handle, System.Threading.ManualResetEvent (System.Threading.EventWaitHandle can be used is well, with the constructor parameter indicating manual reset control). Please see:
http://msdn.microsoft.com/en-us/library/system.threading.manualresetevent%28v=vs.110%29.aspx[^].

For further explanations, please see my past answer: Running exactly one job/thread/process in webservice that will never get terminated (asp.net)[^] (please see the first part of the answer, before the blocking queue, which is also very useful for different things).

For some background, see also: Security on my developed dll[^].

—SA