Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7949603
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T02:02:36+00:00 2026-06-04T02:02:36+00:00

I have a Background worker that needs to be called multiple times based on

  • 0

I have a Background worker that needs to be called multiple times based on the number of checkboxes checked – I have written this to get the checkbox values and put them into a List.

List repSelected = new List();

This is populated and then iterated over like so:

foreach (string rep in repSelected)
{
    backgroundWorker1.RunWorkerAsync(rep);
    backgroundWorker1.RunWorkerCompleted += new RunWorkerCompletedEventHandler(backgroundWorker1_RunWorkerCompleted);
}

The async, DoWork code looks like this:

BackgroundWorker worker = sender as BackgroundWorker;
string rep = e.Argument.ToString();

if (worker.CancellationPending == true)
{
    e.Cancel = true;
}
else
{
    DirectoryExists(rep);
    ProcessRunner(rep); //Rars some large files - expensive
}

The process then runs WorkerComplete, the problem is when the process goes back to do the next iteration of the Worker it crashes out saying the worker is busy – even though the worker has returned it’s WorkerCompleted status.

How can I make sure that the thread is closed before the next iteration of the loop?

NB: I had a conditional on the background worker containing !backgroundWorker1.IsBusy() but this (obviously) just skipped over the remaining iterations without execution.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T02:02:37+00:00Added an answer on June 4, 2026 at 2:02 am

    If you want to process each item in sequence, there is no reason to use a separate backgroundworker for each task. So it will be better to move the foreach loop into the DoWork method. But if you want to process all items in paralell, you need to create one background worker for each item.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a background worker that stops after 100 iterations. Like this: BackgroundWorker bgWorker
lets say i have a background worker in a class that perform db query
Scenario I have a background worker in my application that runs off and does
I have a Ruby on Rails app that needs process many background jobs simultaneously:
I have some code that can spawn background worker threads from anywhere within it.
I have a background worker that performs loading of data from the database into
Background We have worker processes that read jobs from a table in SqlServer then
I have a background worker that does many GUI interactions, but my problem is
I have a ruby app on Heroku that needs to do some background processing
We have a business case that would be perfect for multiple BackgroundWorkers. As an

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.