backgroundworker

Scenario I have a Windows Forms Application. Inside the main form there is a loop that iterates around 3000 times, Creating a new instance of a class on a new thread to perform some calculations. Bearing in mind that this setup uses a Thread Pool, the UI does stay responsive when there are only around 100 iterations of this loop (100 Assets to process). But as soon as this number begins to increase heavily, the UI locks up into eggtimer mode and the thus the log that is writing out to the listbox on the form becomes unreadable. Question Am I right in thinking that the best way around this is

I have question about backgroundworker. I have endless loop in backgroundworker. How can I stop it? Change it to a non-endless loop. The BackgroundWorker has built-in support for cancellation. To cancel a background worker call BackgroundWorker.CancelAsync . Also you need to modify the worker code to check for cancellation as mentioned in the documentation: CancelAsync submits a request to terminate the pending background operation and sets the CancellationPending property to true. When you call CancelAsync, your worker method has an opportunity to stop its execution and exit. The worker code

Threads all share resources. That's the whole problem around multi-threaded operations. MSDN says: You must be careful not to manipulate any user-interface objects in your DoWork event >handler. Instead, communicate to the user interface through the ProgressChanged and RunWorkerCompleted events. BackgroundWorker events are not marshaled across AppDomain boundaries. Do not use a BackgroundWorker component to perform multithreaded operations in more than one AppDomain. And yet when I use the backgroundworker, it's not that I need to be careful not to manipulate any UI objects, it's that can't_

I am trying to update a label from a BackgroundWorker thread that calls a method from another class outside the Form. So I basically want to do this: MainForm.counterLabel.Text = Counter.ToString(); but the label is private. I have looked into things like using BackgroundWorker's progressupdate function, invoke, etc but they don't seem to be what I need. here is some more of my code: the MainForm: clickThread.DoWork += (s, o) => { theClicker.Execute(speed); }; clickThread.RunWorkerAsync(); The Class/Method called: public void Execute(int speed) { while (running) { Thread.Sleep(speed); Mouse

In my program I have two methods that takes a while to complete, about few minutes each. While these methods are being executed, I display a Progress Bar in a separate window which shows the progress of each method. My two methods are in a static Utility class. They look like the following: public static class Utility { public static bool TimeConsumingMethodOne(object sender) { for (int i = 1; i <= 100; i++) { Thread.Sleep(100); (sender as BackgroundWorker).ReportProgress(i); } return true; } public static bool TimeConsumingMethodTwo(object sender) { for (int i = 1; i <= 100; i++) { Thread

I'm quite new to WPF. I am developing a PRISM application and want to update the UI when an enumerable is updated. I use a backgroundWorker in my modelView to update the enumaration. it all works fine until the enumeration it self gets updated and then the UI freezes!! a friend told my I might be able to use the yield keyword but I didn't quite figured it out. Here is the code: public void ChangeCollection() { BackgroundWorker worker = new BackgroundWorker(); // Set workers job worker.DoWork += (sender, e) => { RunOnUIThread(() => IsBusy = true); e.Result = GetPrimes(); }; // On Complete

I have a windows form which utilizes a backgroundworker. The backgroundworker instantiates an object and then executes a method in that object. My problem is that when I use backgroundworker.CancelAsync the method running on the remote object does not stop. In the example below, the dowork method continues to execute after button cancel is clicked. FYI, dowork is looping thru a spreadsheet and doing some data manipulation based on the rows in the spreadsheet. private void backgroundWorker1_DoWork(object sender, DoWorkEventArgs e) { myObject newObject = new myObject(); newObject.dowork(); if