Well one thing you will definitely have to watch out for is your files being locked by one thread while a different thread is trying to access it too. What I am trying to say is that if you have three I/O tasks to perform on a file, you can only do one I/O operation at a time. You cannot write to a file at the same time you try to read from a file. So I would recommend three seperate background workers. When the first I/O operation completes, in the worker.RunWorkerCompleted start your next operation and so forth.

I need your ideas to proceed with BackGroundWorker threads for my requirement.

I have a C# Windows Application that processes a directory/sub-directories containing huge number of .xml files, say 100,000 files and perfoms time-consuming I/O operation such as parsing xml files(I am currently querying those files using Linq) while updating the user of every file being processed. In fact, I have 3 such I/O operations to be performed on the same set of files(so all the 3 tasks will basically share the same resources/directory/files for their own independent requirements).

Also, I currently have a Windows Form associated with 3 different class files, one for each I/O task. I need to implement multithreading so that I can run all the 3 tasks at the same time, while updating the UI controls such as Label- one per task/thread to keep the user informed about the background process.

What is the best way of proceeding about such kind of task in a single application?(if possible..). Kindly suggest me.

Thanks in advance

Very Nice article, very clearly explained!!!

I declared a withevents private variable at page level and used the regular event handlers as you mentioned.

Thanks for your reply.

Since VB doesn’t have anonymous delegates just use regular event handlers

Any help on converting the below and relating function to vb would be much appreciated.

worker.DoWork = delegate(object s, DoWorkEventArgs args){

}

This is an example of how I would use it with “Processing” being the UserState.

worker.ReportProgress(percentage, “Processing”);

Then get the UserState in the ProgressChanged event handler

text = string.Format(”{0} {1}%”, args.UserState.ToString(), args.ProgressPercentage.ToString());

That’s good question. One problem with BackgroundWorker is the fact that you cannot pass anything through userState in ReportProgress, because it will be always null – it’s a bug in .NET IMO.