Skip to main content

C#: Using the Background Worker to thread your application processing.

In this article I go over using the background worker control in C# .NET Framework (Visual Studio 2015). This control allows you to easily do processing intensive tasks without locking up your interface thread. I use this a lot in winforms applications where I expect code to take any amount of time that the user would notice the interface being locked up while processing. This control gives you the ability to send progress updates to the interface thread as well as cancel processing any any time.

The code for this example is on my GitHub here.

https://www.youtube.com/watch?v=PKKRAyn3TTs

Here is the important code from the main form:


public enum CurrentStatus
{
    None,
    Reset,
    Loading,
    Cancelled,
    Success,
    Busy
}

public class MainForm : Form
{
    private BackgroundWorker bwInstance;
    private Button btnStartWorker;
    private Button btnStopWorker;
    private Label lblLoadingStatus;
    private ProgressBar prgLoadingProgress;

    private CurrentStatus processingStatus = CurrentStatus.None;

    public MainForm()
    {
        InitializeComponents();
        bwInstance = new BackgroundWorker();
        bwInstance.WorkerReportsProgress = true;
        bwInstance.DoWork += bwInstance_DoWork;
        bwInstance.ProgressChanged += bwInstance_ProgressChanged;
        bwInstance.RunWorkerCompleted += bwInstance_RunWorkerCompleted;
    }

    private void InitializeComponents()
    {
        // Initialize UI components here
    }

    private void setFormControlsBasedOnStatus()
    {
        switch (processingStatus)
        {
            case CurrentStatus.None:
                break;
            case CurrentStatus.Reset:
                btnStartWorker.Enabled = true;
                btnStopWorker.Enabled = false;
                lblLoadingStatus.Visible = false;
                lblLoadingStatus.Text = "Loading...";
                prgLoadingProgress.Value = 0;
                break;
            case CurrentStatus.Loading:
                btnStartWorker.Enabled = false;
                btnStopWorker.Enabled = true;
                lblLoadingStatus.Visible = true;
                lblLoadingStatus.Text = "Loading...";
                prgLoadingProgress.Value = 0;
                break;
            case CurrentStatus.Cancelled:
                btnStartWorker.Enabled = true;
                btnStopWorker.Enabled = false;
                lblLoadingStatus.Visible = true;
                lblLoadingStatus.Text = "Cancelled";
                prgLoadingProgress.Value = 0;
                break;
            case CurrentStatus.Success:
                btnStartWorker.Enabled = true;
                btnStopWorker.Enabled = false;
                lblLoadingStatus.Visible = true;
                lblLoadingStatus.Text = "Success!";
                prgLoadingProgress.Value = 0;
                break;
            case CurrentStatus.Busy:
                btnStartWorker.Enabled = true;
                btnStopWorker.Enabled = false;
                lblLoadingStatus.Visible = true;
                lblLoadingStatus.Text = "The worker is busy.";
                prgLoadingProgress.Value = 0;
                break;
            default:
                break;
        }
    }

    private bool isWorkerBeingCancelled(BackgroundWorker worker, DoWorkEventArgs e)
    {
        bool returnValue = false;
        if (worker.CancellationPending)
        {
            e.Cancel = true;
            returnValue = true;
            processingStatus = CurrentStatus.Cancelled;
        }
        return returnValue;
    }

    private void bwInstance_DoWork(object sender, DoWorkEventArgs e)
    {
        BackgroundWorker worker = sender as BackgroundWorker;
        if (isWorkerBeingCancelled(worker, e)) return;

        worker.ReportProgress(20);
        System.Threading.Thread.Sleep(250);

        if (isWorkerBeingCancelled(worker, e)) return;
        worker.ReportProgress(40);
        System.Threading.Thread.Sleep(250);

        if (isWorkerBeingCancelled(worker, e)) return;
        worker.ReportProgress(60);
        System.Threading.Thread.Sleep(250);

        if (isWorkerBeingCancelled(worker, e)) return;
        worker.ReportProgress(80);
        System.Threading.Thread.Sleep(250);

        if (isWorkerBeingCancelled(worker, e)) return;
        worker.ReportProgress(100);
        System.Threading.Thread.Sleep(250);

        processingStatus = CurrentStatus.Success;
    }

    private void bwInstance_ProgressChanged(object sender, ProgressChangedEventArgs e)
    {
        prgLoadingProgress.Value = e.ProgressPercentage;
    }

    private void bwInstance_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)
    {
        setFormControlsBasedOnStatus();
    }

    private void btnStartWorker_Click(object sender, EventArgs e)
    {
        if (!bwInstance.IsBusy)
        {
            processingStatus = CurrentStatus.Loading;
            setFormControlsBasedOnStatus();
            bwInstance.RunWorkerAsync();
        }
        else
        {
            processingStatus = CurrentStatus.Busy;
            setFormControlsBasedOnStatus();
        }
    }

    private void btnStopWorker_Click(object sender, EventArgs e)
    {
        bwInstance.CancelAsync();
    }
}

I made a status enumeration with a form-level variable that holds the current processing status. I also have a function to update the interface based on that status enum. The background worker is called to see if is busy, if not, the worker is started. Throughout processing, we check to see if the user cancelled the work and also update the progress control by pushing a numeric value (0-100 to match our progress control) through the worker into the interface thread. When the cancel button is clicked, it sets a value in the background worker that we can track to stop processing as needed. I have a function that is called throughout processing that will break out of the processing function and set our enum status variable telling the system that processing was cancelled. 


Popular posts from this blog

ChatGPT is a new, and faster, way to do programming!

Currently ChatGPT is in a free “initial research preview” . One of its well known use cases at this point is generating software code. I’ve also just used it to write most of this article… Well, actually a future article about cleaning up SRT subtitle files of their metadata faster than I have been by hand with Notepad++ and its replace functionality. Update: I recorded a screencast of writing the SRT subtitle cleaner application loading and processing portion. I relied heavily on ChatGPT for code. It was a fun process! https://youtu.be/TkEW39OloUA ChatGPT, developed by OpenAI, is a powerful language model that can assist developers in a variety of tasks, including natural language processing and text generation. One such task that ChatGPT can help with is creating an SRT cleaner program. SRT, or SubRip Subtitle, files are commonly used to add subtitles to video files. However, these files can become cluttered with unnecessary information, such as timing lines or blank spaces. To clean...

Theme error in 2010s Android App after AppCompat Migration

I plan on releasing a lot of my old work as GPL open source, but most of it has aged to the point that it no longer functions, or if it does work it’s running in compatibility mode. Basically it’s no longer best practices. Not a good way to start off any new public GPL projects, in my opinion. The current project I’m working on is an Android app that calculates star trails meant to help photographers get or avoid that in their night time photos. For now I’m going to skip some of the import process because I didn’t document it exactly. It’s been mostly trial and error as I poke around Android Studio post import. The Android Studio import process… Removing Admob Google Play code before the project would run at all. After removing dependencies, it kind of worked, but when running it in the emulator it shows a pop-up message saying that the app was developed for an old version of Android. Going through the process of updating code to match current best practices… I had the IDE convert the ...

Blogger Notable theme pop-up header issue fix (thanks to Gemini Pro)

I've made a few half hearted attempts over the years to to fix Blogger's Notable theme's rendering of the pop-up header that shows up when you scroll down the page a decent amount and then pull back to reveal that secondary header. On Chrome mobile I noticed a gray box that forms next to the magnifying glass icon. I never looked in detail on  Chrome desktop, but it had an issue as well which I'll detail below.  If you are looking for a solution and don't want all of the extra talk about how I was able to find it, here it is:  .centered-top-container .sticky .main_header_elements { overflow : hidden !important ; } I decided to try using Gemini Pro 2.5 to see if it was capable of finding the issue and giving me a fix. Turns out that it was able, but it took a bit of collaboration back and forth to find the actual problem.  Here is a modified article I asked it to give me based on our debugging chat (it was very colorful in the article which I scaled back a lot, ...