backgroundworker

During the start of my windows application, I have to make a call to a web service to retrieve some default data to load onto my application. During the load of the form, I run a backgroundworker to retrieve this data. I want to display the wait cursor until this data is retrieved. How would I do this? I've tried setting the wait cursor before calling the backgroundworker to run. When I report a progress of 100 then I set it back to the default cursor. The wait cursor comes up but when I move the mouse it disappears. Environment: Windows 7 Pro 64-bit VS2010 C# .NET 4.0 Windows Forms EDIT: I am

My application writes a log file (currently using log4net ). I'd like to setup a timer and a background worker to read the log file and print its content into some control in my form, while it's being written. I can't use the FileSystemWatcher class because seems broken: sometimes the event "changed" fires, sometimes do not. And it has an extremely low "pooling rate". So I created a Timer and a FileSystemWatcher. On the "tick" event of the timer, the background worker does its job. The question is: how to read only the lines that are added since the last check of the worker? public LogForm() {

I am setting the DataContext of an object in the completed method of a background worker thread. For some reason, I get an error saying: Cannot modify the logical children for this node at this time because a tree walk is in progress pointing to the Chart1.DataContext=allDates line. What does a tree walk is in progress mean? I've tried doing this set using a Dispatcher operation as well and that gives the same error... Any ideas? Google yeilds nothing on this error message. The code taht's causing this is internal to Microsoft's Charting toolkit... I wonder if I've found a bug in their control

I am trying to use the .NET Backgroundworker Object in an application I am developing. All the material on the internet say that this object runs in the "background" but nowhere have I been able to confirm that this background thread indeed runs in a "low priority" mode . This question arises because in Windows (I assume) a background task can run in a 'normal' or 'below normal' or 'low' priority mode. In my application, I tried to set the priority myself inside the DoWork function by calling ... Thread.CurrentThread.Priority=ThreadPriority.Lowest ... but this seems to have no effect. Does the

I have 2 kinds of C# WPF app projects: based on .NET 4.0 that I cannot migrate to .NET 4.5 based on .NET 4.0 that I can migrate to .NET 4.5 All of them should spawn 2-10 long-running (days) processes which can be cancelled and re-launched by users. I am interested to follow the best design practices. First of all, now, I am interested to disambiguate about BackgroundWorker usage though, I hope, my question should be valid about other asynchronous patterns. I see (contradicting) concurrent points of view about Asynchronous Programming Model (APM) Event-based Asynchronous Pattern (EAP)