Home/ Questions/Q 413351
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T18:10:32+00:00

Taken as given that multi-threaded applications are debugging hell and should be avoided at

  • 0

Taken as given that multi-threaded applications are debugging hell and should be avoided at all costs…

Is the requirement to display of a progress bar a sufficient reason to enter multi-threaded land?

Specifically, let’s say a C# windows forms .NET 3.0 application needs to download a 100MB file. Is it right to multi-thread (via a BackgroundWorker component) to do the download on that thread so that the UI thread is free to update a progress bar showing progress?

Sorry if this question is a bit fuzzy. I’ve not done anything multi-threaded before.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have not said anything about what language are you using; in C#, for instance, you could use WebClient with DownloadFileAsync and DownloadProgressChanged

    While this is a multi-threaded program, I consider it as low complexity program.

    • 0