If some method takes a lot of time, should I implement it as asynchronous?
Or maybe use synchronous in another Thread (e.g. using BackgroundWorker)?
If some method takes a lot of time, should I implement it as asynchronous?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
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.
If some method takes a lot of time, should I implement it as asynchronous?
Or maybe use synchronous in another Thread (e.g. using BackgroundWorker)?
Asychronous calling is used when you have work items that should be handled in the background and you care when they finish
Use BackgroundWorker if you have a single task that runs in the background and needs to interact with the UI. and use it if you don’t care when they finish their task. The task of marshalling data and method calls to the UI thread are handled automatically through its event-based model.
Avoid BackgroundWorker if (1) your assembly does not already reference the System.Windows.Form assembly, (2) you need the thread to be a foreground thread, or (3) you need to manipulate the thread priority.