# c# – How and when to use ‘async’ and ‘await’

## The Question :

1129 people think this question is useful

From my understanding one of the main things that async and await do is to make code easy to write and read – but is using them equal to spawning background threads to perform long duration logic?

I’m currently trying out the most basic example. I’ve added some comments inline. Can you clarify it for me?

// I don't understand why this method must be marked as async.
private async void button1_Click(object sender, EventArgs e)
{

// this line is reached after the 5 seconds sleep from
// DoSomethingAsync() method. Shouldn't it be reached immediately?
int a = 1;

// from my understanding the waiting should be done here.
int x = await access;
}

{
// is this executed on a background thread?
return 1;
}


• Also, in your example notice that you get a warning when you compile the code above. Pay attention to the warning. It is telling you that this code doesn’t make sense.

787 people think this answer is useful

When using async and await the compiler generates a state machine in the background.

Here’s an example on which I hope I can explain some of the high-level details that are going on:

public async Task MyMethodAsync()
{
// independent work which doesn't need the result of LongRunningOperationAsync can be done here

//and now we call await on the task
//use the result
Console.WriteLine(result);
}

public async Task<int> LongRunningOperationAsync() // assume we return an int from this long running operation
{
await Task.Delay(1000); // 1 second delay
return 1;
}



OK, so what happens here:

1. Task<int> longRunningTask = LongRunningOperationAsync(); starts executing LongRunningOperation

2. Independent work is done on let’s assume the Main Thread (Thread ID = 1) then await longRunningTask is reached.

Now, if the longRunningTask hasn’t finished and it is still running, MyMethodAsync() will return to its calling method, thus the main thread doesn’t get blocked. When the longRunningTask is done then a thread from the ThreadPool (can be any thread) will return to MyMethodAsync() in its previous context and continue execution (in this case printing the result to the console).

A second case would be that the longRunningTask has already finished its execution and the result is available. When reaching the await longRunningTask we already have the result so the code will continue executing on the very same thread. (in this case printing result to console). Of course this is not the case for the above example, where there’s a Task.Delay(1000) involved.

181 people think this answer is useful

From my understanding one of the main things that async and await do is to make code easy to write and read.

They’re to make asynchronous code easy to write and read, yes.

Is it the same thing as spawning background threads to perform long duration logic?

Not at all.

// I don’t understand why this method must be marked as ‘async’.

The async keyword enables the await keyword. So any method using await must be marked async.

// This line is reached after the 5 seconds sleep from DoSomethingAsync() method. Shouldn’t it be reached immediately?

No, because async methods are not run on another thread by default.

// Is this executed on a background thread?

No.

You may find my async/await intro helpful. The official MSDN docs are also unusually good (particularly the TAP section), and the async team put out an excellent FAQ.

176 people think this answer is useful

## Explanation

Here is a quick example of async/await at a high level. There are a lot more details to consider beyond this.

Note: Task.Delay(1000) simulates doing work for 1 second. I think it’s best to think of this as waiting for a response from an external resource. Since our code is waiting for a response, the system can set the running task off to the side and come back to it once it’s finished. Meanwhile, it can do some other work on that thread.

In the example below, the first block is doing exactly that. It starts all the tasks immediately (the Task.Delay lines) and sets them off to the side. The code will pause on the await a line until the 1 second delay is done before going to the next line. Since b, c, d, and e all started executing at almost the exact same time as a (due to lack of the await), they should finish at roughly the same time in this case.

In the example below, the second block is starting a task and waiting for it to finish (that is what await does) before starting the subsequent tasks. Each iteration of this takes 1 second. The await is pausing the program and waiting for the result before continuing. This is the main difference between the first and second blocks.

## Example

Console.WriteLine(DateTime.Now);

// This block takes 1 second to run because all
// 5 tasks are running simultaneously
{

await a;
await b;
await c;
await d;
await e;
}

Console.WriteLine(DateTime.Now);

// This block takes 5 seconds to run because each "await"
// pauses the code until the task finishes
{
}
Console.WriteLine(DateTime.Now);



OUTPUT:

5/24/2017 2:22:50 PM
5/24/2017 2:22:51 PM (First block took 1 second)
5/24/2017 2:22:56 PM (Second block took 5 seconds)



## Extra info regarding SynchronizationContext

Note: This is where things get a little foggy for me, so if I’m wrong on anything, please correct me and I will update the answer. It’s important to have a basic understanding of how this works but you can get by without being an expert on it as long as you never use ConfigureAwait(false), although you will likely lose out on some opportunity for optimization, I assume.

There is one aspect of this which makes the async/await concept somewhat trickier to grasp. That’s the fact that in this example, this is all happening on the same thread (or at least what appears to be the same thread in regards to its SynchronizationContext). By default, await will restore the synchronization context of the original thread that it was running on. For example, in ASP.NET you have an HttpContext which is tied to a thread when a request comes in. This context contains things specific to the original Http request such as the original Request object which has things like language, IP address, headers, etc. If you switch threads halfway through processing something, you could potentially end up trying to pull information out of this object on a different HttpContext which could be disastrous. If you know you won’t be using the context for anything, you can choose to “not care” about it. This basically allows your code to run on a separate thread without bringing the context around with it.

How do you achieve this? By default, the await a; code actually is making an assumption that you DO want to capture and restore the context:

await a; //Same as the line below
await a.ConfigureAwait(true);



If you want to allow the main code to continue on a new thread without the original context, you simply use false instead of true so it knows it doesn’t need to restore the context.

await a.ConfigureAwait(false);



After the program is done being paused, it will continue potentially on an entirely different thread with a different context. This is where the performance improvement would come from — it could continue on on any available thread without having to restore the original context it started with.

Is this stuff confusing? Hell yeah! Can you figure it out? Probably! Once you have a grasp of the concepts, then move on to Stephen Cleary’s explanations which tend to be geared more toward someone with a technical understanding of async/await already.

150 people think this answer is useful

Further to the other answers, have a look at await (C# Reference)

and more specifically at the example included, it explains your situation a bit

The following Windows Forms example illustrates the use of await in an async method, WaitAsynchronouslyAsync. Contrast the behavior of that method with the behavior of WaitSynchronously. Without an await operator applied to a task, WaitSynchronously runs synchronously despite the use of the async modifier in its definition and a call to Thread.Sleep in its body.

private async void button1_Click(object sender, EventArgs e)
{
// Call the method that runs asynchronously.
string result = await WaitAsynchronouslyAsync();

// Call the method that runs synchronously.
//string result = await WaitSynchronously ();

// Display the result.
textBox1.Text += result;
}

// The following method runs asynchronously. The UI thread is not
// blocked during the delay. You can move or resize the Form1 window
{
return "Finished";
}

// The following method runs synchronously, despite the use of async.
// You cannot move or resize the Form1 window while Thread.Sleep
// is running because the UI thread is blocked.
{
return "Finished";
}



64 people think this answer is useful

Showing the above explanations in action in a simple console program:

class Program
{
static void Main(string[] args)
{
TestAsyncAwaitMethods();
Console.WriteLine("Press any key to exit...");
}

public async static void TestAsyncAwaitMethods()
{
await LongRunningMethod();
}

{
Console.WriteLine("Starting Long Running method...");
Console.WriteLine("End Long Running method...");
return 1;
}
}



And the output is:

Starting Long Running method...
Press any key to exit...
End Long Running method...



Thus,

1. Main starts the long running method via TestAsyncAwaitMethods. That immediately returns without halting the current thread and we immediately see ‘Press any key to exit’ message
2. All this while, the LongRunningMethod is running in the background. Once its completed, another thread from Threadpool picks up this context and displays the final message

45 people think this answer is useful

I think you’ve picked a bad example with System.Threading.Thread.Sleep

Point of an async Task is to let it execute in background without locking the main thread, such as doing a DownloadFileAsync

System.Threading.Thread.Sleep isn’t something that is “being done”, it just sleeps, and therefore your next line is reached after 5 seconds …

Read this article, I think it is a great explanation of async and await concept: http://msdn.microsoft.com/en-us/library/vstudio/hh191443.aspx

39 people think this answer is useful

For fastest learning..

• Understand method execution flow(with a diagram): 3 mins

• Question introspection (learning sake): 1 min

• Quickly get through syntax sugar: 5 mins

• Share the confusion of a developer : 5 mins

• Problem: Quickly change a real-world implementation of normal code to Async code: 2 mins

• Where to Next?

Understand method execution flow(with a diagram): 3 mins

In this image, just focus on #6 (nothing more)

At #6 step, execution ran out of work and stopped. To continue it needs a result from getStringTask(kind of a function). Therefore, it uses an await operator to suspend its progress and give control back(yield) to the caller(of this method we are in). The actual call to getStringTask was made earlier in #2. At #2 a promise was made to return a string result. But when will it return the result? Should we(#1:AccessTheWebAsync) make a 2nd call again? Who gets the result, #2(calling statement) or #6(awaiting statement)

The external caller of AccessTheWebAsync() also is waiting now. So caller waiting for AccessTheWebAsync, and AccessTheWebAsync is waiting for GetStringAsync at the moment. Interesting thing is AccessTheWebAsync did some work(#4) before waiting perhaps to save time from waiting. The same freedom to multitask is also available for the external caller(and all callers in the chain) and this is the biggest plus of this ‘async’ thingy! You feel like it is synchronous..or normal but it is not.

#2 and #6 is split so we have the advantage of #4(work while waiting). But we can also do it without splitting. string urlContents = await client.GetStringAsync("...");. Here we see no advantage but somewhere in the chain one function will be splitting while rest of them call it without splitting. It depends which function/class in the chain you use. This change in behavior from function to function is the most confusing part.

Remember, the method was already returned(#2), it cannot return again(no second time). So how will the caller know? It is all about Tasks! Task was returned. Task status was waited for (not method, not value). Value will be set in Task. Task status will be set to complete. Caller just monitors Task(#6). So 6# is the answer to where/who gets the result. Further reads for later here.

Question introspection for learning sake: 1 min

Let us adjust the question a bit:

How and When to use async and await Tasks?

Because learning Task automatically covers the other two(and answers your question)

Quickly get through syntax sugar: 5 mins

• Original non-async method
internal static int Method(int arg0, int arg1)
{
int result = arg0 + arg1;
IO(); // Do some long running IO.
return result;
}


• a brand new Task-ified method to call the above method
internal static Task<int> MethodTask(int arg0, int arg1)
{
}



Did we mention await or async? No. Call the above method and you get a task which you can monitor. You already know what the task returns.. an integer.

• Calling a Task is slightly tricky and that is when the keywords starts to appear. If there was a method calling the original method(non-async) then we need to edit it as given below. Let us call MethodTask()
internal static async Task<int> MethodAsync(int arg0, int arg1)
{
int result = await HelperMethods.MethodTask(arg0, arg1);
return result;
}



Same code above added as image below:

1. We are ‘awaiting’ task to be finished. Hence the await(mandatory syntax)
2. Since we use await, we must use async(mandatory syntax)
3. MethodAsync with Async as the prefix (coding standard)

await is easy to understand but the remaining two (async,Async) may not be :). Well, it should make a lot more sense to the compiler though.Further reads for later here

So there are 2 parts.

2. Create syntactic sugar to call the task with await+async(this involves changing existing code if you are converting a non-async method)

Remember, we had an external caller to AccessTheWebAsync() and that caller is not spared either… i.e it needs the same await+async too. And the chain continues(hence this is a breaking change which could affect many classes). It can also be considered a non-breaking change because the original method is still there to be called. Change it’s access if you want to impose a breaking change and then the classes will be forced to use Task-method. Or just delete the method and move it to task-method. Anyways, in an async call there will always be a Task at one end and only one.

All okay, but one developer was surprised to see Task missing…

Share the confusion of a developer: 5 mins

A developer has made a mistake of not implementing Task but it still works! Try to understand the question and just the accepted answer provided here. Hope you have read and fully understood. The summary is that we may not see/implement ‘Task’ but it is implemented somewhere in a parent/associated class. Likewise in our example calling an already built MethodAsync() is way easier than implementing that method with a Task (MethodTask()) ourself. Most developers find it difficult to get their head around Tasks while converting a code to Asynchronous one.

Tip: Try to find an existing Async implementation (like MethodAsync or ToListAsync) to outsource the difficulty. So we only need to deal with Async and await (which is easy and pretty similar to normal code)

Problem: Quickly change a real-world implementation of normal code to Async operation: 2 mins

Code line shown below in Data Layer started to break(many places). Because we updated some of our code from .Net framework 4.2.* to .Net core. We had to fix this in 1 hour all over the application!

var myContract = query.Where(c => c.ContractID == _contractID).First();



easypeasy!

1. We installed EntityFramework nuget package because it has QueryableExtensions. Or in other words it does the Async implementation(task), so we could survive with simple Async and await in code.
2. namespace = Microsoft.EntityFrameworkCore

calling code line got changed like this

var myContract = await query.Where(c => c.ContractID == _contractID).FirstAsync();


1. Method signature changed from

Contract GetContract(int contractnumber)

to

async Task<Contract> GetContractAsync(int contractnumber)

1. calling method also got affected: GetContractAsync(123456); was called as GetContractAsync(123456).Result;

2. We changed it everywhere in 30 minutes!

But the architect told us not to use EntityFramework library just for this! oops! drama! Then we made a custom Task implementation(yuk). Which you know how. Still easy! ..still yuk..

Where to Next? There is a wonderful quick video we could watch about Converting Synchronous Calls to Asynchronous in ASP.Net Core, perhaps that is likely the direction one would go after reading this. Or have I explained enough? 😉

25 people think this answer is useful

Here is a quick console program to make it clear to those who follow. The TaskToDo method is your long running method that you want to make async. Making it run async is done by the TestAsync method. The test loops method just runs through the TaskToDo tasks and runs them async. You can see that in the results because they don’t complete in the same order from run to run – they are reporting to the console UI thread when they complete. Simplistic, but I think the simplistic examples bring out the core of the pattern better than more involved examples:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace TestingAsync
{
class Program
{
static void Main(string[] args)
{
TestLoops();
}

private static async void TestLoops()
{
for (int i = 0; i < 100; i++)
{
await TestAsync(i);
}
}

{
}

private async static void TaskToDo(int i)
{
Console.WriteLine(i);
}
}
}



16 people think this answer is useful

All the answers here use Task.Delay() or some other built in async function. But here is my example that use none of those async functions:

// Starts counting to a large number and then immediately displays message "I'm counting...".
// Then it waits for task to finish and displays "finished, press any key".
static void asyncTest ()
{
Console.WriteLine("Started asyncTest()");
task.Wait(); // if you comment this line you will see that message "Finished counting" will be displayed before we actually finished counting.
Console.WriteLine("Finished counting.");
Console.WriteLine("Press any key to exit program.");
}

{
long k = 0;
Console.WriteLine("Started asyncTest_count()");
{
long countTo = 100000000;
int prevPercentDone = -1;
for (long i = 0; i <= countTo; i++)
{
int percentDone = (int)(100 * (i / (double)countTo));
if (percentDone != prevPercentDone)
{
prevPercentDone = percentDone;
Console.Write(percentDone.ToString() + "% ");
}

k = i;
}
});
Console.WriteLine("");
Console.WriteLine("Finished asyncTest_count()");
return k;
}



14 people think this answer is useful

# Async & Await Simple Explanation

Simple Analogy

A person may wait for their morning train. This is all they are doing as this is their primary task that they are currently performing. (synchronous programming (what you normally do!))

Another person may await their morning train whilst they smoke a cigarette and then drink their coffee. (Asynchronous programming)

What is asynchronous programming?

Asynchronous programming is where a programmer will choose to run some of his code on a separate thread from the main thread of execution and then notify the main thread on it’s completion.

What does the async keyword actually do?

Prefixing the async keyword to a method name like

async void DoSomething(){ . . .



allows the programmer to use the await keyword when calling asynchronous tasks. That’s all it does.

Why is this important?

In a lot of software systems the main thread is reserved for operations specifically relating to the User Interface. If I am running a very complex recursive algorithm that takes 5 seconds to complete on my computer, but I am running this on the Main Thread (UI thread) When the user tries to click on anything on my application, it will appear to be frozen as my main thread has queued and is currently processing far too many operations. As a result the main thread cannot process the mouse click to run the method from the button click.

When do you use Async and Await?

Use the asynchronous keywords ideally when you are doing anything that doesn’t involve the user interface.

So lets say you’re writing a program that allows the user to sketch on their mobile phone but every 5 seconds it is going to be checking the weather on the internet.

We should be awaiting the call the polling calls every 5 seconds to the network to get the weather as the user of the application needs to keep interacting with the mobile touch screen to draw pretty pictures.

How do you use Async and Await

Following on from the example above, here is some pseudo code of how to write it:

    //ASYNCHRONOUS
//this is called using the await keyword every 5 seconds from a polling timer or something.

{
var weather = await GetWeather();
//do something with the weather now you have it
}

{

return deserializeJson<weatherJson>(weatherJson);
}

//SYNCHRONOUS
//This method is called whenever the screen is pressed
void ScreenPressed()
{
DrawSketchOnScreen();
}



I forgot to mention in my original notes that in C# you can only await methods that are wrapped in Tasks. for example you may await this method:

// awaiting this will return a string.
// calling this without await (synchronously) will result in a Task<string> object.



You cannot await methods that are not tasks like this:

async string FetchHelloWorld() {..



Feel free to review the source code for the Task class here.

13 people think this answer is useful

This answer aims to provide some info specific to ASP.NET.

By utilizing async/await in MVC controller, it is possible to increase thread pool utilization and achieve a much better throughput, as explained in the below article,

http://www.asp.net/mvc/tutorials/mvc-4/using-asynchronous-methods-in-aspnet-mvc-4

In web applications that sees a large number of concurrent requests at start-up or has a bursty load (where concurrency increases suddenly), making these web service calls asynchronous will increase the responsiveness of your application. An asynchronous request takes the same amount of time to process as a synchronous request. For example, if a request makes a web service call that requires two seconds to complete, the request takes two seconds whether it is performed synchronously or asynchronously. However, during an asynchronous call, a thread is not blocked from responding to other requests while it waits for the first request to complete. Therefore, asynchronous requests prevent request queuing and thread pool growth when there are many concurrent requests that invoke long-running operations.

11 people think this answer is useful

## Async / Await

Actually Async / Await are a pair of keywords which are just syntactic sugar for creating a callback of an asynchronous task.

Take by example this operation:

    public static void DoSomeWork()
{
{

// IS NOT bubbling up due to the different threads
throw new Exception();

return "Hello";
});

// This is the callback
// -> Exception is swallowed silently
Console.WriteLine("Completed");

});
}



The code above has several disadvantages. Errors are not passed on and it’s hard to read. But Async and Await come in to help us out:

    public async static void DoSomeWork()
{
var result = await Task.Run(() =>
{

// IS bubbling up
throw new Exception();

return "Hello";
});

// every thing below is a callback
// (including the calling methods)

Console.WriteLine("Completed");

}



Await calls have to be in Async methods. This has some advantages:

• Returns the result of the Task
• creates automatically a callback
• checks for errors and lets them bubble up in callstack (only up to none-await calls in callstack)
• waits for the result
• frees up the main thread
• runs the callback on the main thread
• makes the code easy to read
• and a lot more

NOTE: Async and Await are used with asynchronous calls not to make these. You have to use Task Libary for this, like Task.Run() .

Here is a comparison between await and none await solutions

This is the none async solution:

    public static long DoTask()
{
stopWatch.Reset();
stopWatch.Start();

});
// goes directly further
// WITHOUT waiting until the task is finished

stopWatch.Stop();
// 50 milliseconds
return stopWatch.ElapsedMilliseconds;
}



This is the async method:

    public async static Task<long> DoAwaitTask()
{
stopWatch.Reset();
stopWatch.Start();

});
// Waits until task is finished

stopWatch.Stop();
// 2050 milliseconds
return stopWatch.ElapsedMilliseconds;
}



You can actually call an async method without the await keyword but this means that any Exception here are swallowed in release mode:

    public static Stopwatch stopWatch { get; } = new Stopwatch();

static void Main(string[] args)
{
// 2050 (2000 more because of the await)
// 50
}



Async and Await are not meant for parallel computing. They are used to not block your main thread. When it’s about asp.net or Windows applications, blocking your main thread due to a network call is a bad thing. If you do this, your app will get unresponsive or even crash.

Check out ms docs for more examples.

10 people think this answer is useful

To be honest I still think the best explanation is the one about future and promises on the Wikipedia: http://en.wikipedia.org/wiki/Futures_and_promises

The basic idea is that you have a separate pool of threads that execute tasks asynchronously. When using it. The object does however make the promise that it will execute the operation at some time and give you the result when you request it. This means that it will block when you request the result and hasn’t finished, but execute in the thread pool otherwise.

From there you can optimize things: some operations can be implemented async and you can optimize things like file IO and network communication by batching together subsequent requests and/or reordering them. I’m not sure if this is already in the task framework of Microsoft – but if it isn’t that would be one of the first things I would add.

You can actually implement the future pattern sort-of with yields in C# 4.0. If you want to know how it works exactly, I can recommend this link that does a decent job: http://code.google.com/p/fracture/source/browse/trunk/Squared/TaskLib/ . However, if you start toying with it yourself, you will notice that you really need language support if you want to do all the cool things — which is exactly what Microsoft did.

9 people think this answer is useful

See this fiddle https://dotnetfiddle.net/VhZdLU (and improve it if possible) for running a simple console application which shows usages of Task, Task.WaitAll(), async and await operators in the same program.

This fiddle should clear your execution cycle concept.

Here is the sample code

using System;

public class Program
{
public static void Main()
{
var a = MyMethodAsync(); //Task started for Execution and immediately goes to Line 19 of the code. Cursor will come back as soon as await operator is met
Console.WriteLine("Cursor Moved to Next Line Without Waiting for MyMethodAsync() completion");
Console.WriteLine("Now Waiting for Task to be Finished");
Console.WriteLine("Exiting CommandLine");
}

{
// independent work which doesn't need the result of LongRunningOperationAsync can be done here
Console.WriteLine("Independent Works of now executes in MyMethodAsync()");
//and now we call await on the task
//use the result
Console.WriteLine("Result of LongRunningOperation() is " + result);
}

public static async Task<int> LongRunningOperation() // assume we return an int from this long running operation
{
Console.WriteLine("LongRunningOperation() Started");
await Task.Delay(2000); // 2 second delay
Console.WriteLine("LongRunningOperation() Finished after 2 Seconds");
return 1;
}

}



Trace coming from Output Window:

3 people think this answer is useful

The way I understand it is also, there should be a third term added to the mix: Task.

Async is just a qualifier you put on your method to say it’s an asynchronous method.

Task is the return of the async function. It executes asynchronously.

You await a Task. When code execution reaches this line, control jumps out back to caller of your surrounding original function.

If instead, you assign the return of an async function (ie Task) to a variable, when code execution reaches this line, it just continues past that line in the surrounding function while the Task executes asynchronously.

3 people think this answer is useful
public static void Main(string[] args)
{
}

// You use the async keyword to mark a method for asynchronous operations.
// The "async" modifier simply starts synchronously the current thread.
// What it does is enable the method to be split into multiple pieces.
// The boundaries of these pieces are marked with the await keyword.
{
using (HttpClient client = new HttpClient())
{
// When you use the await keyword, the compiler generates the code that checks if the asynchronous operation is finished.
// If it is already finished, the method continues to run synchronously.
// If not completed, the state machine will connect a continuation method that must be executed WHEN the Task is completed.

// Http request example.
// (In this example I can set the milliseconds after "sleep=")
String result = await client.GetStringAsync("http://httpstat.us/200?sleep=1000");

Console.WriteLine(result);

// After completing the result response, the state machine will continue to synchronously execute the other processes.

return result;
}
}



3 people think this answer is useful

On a higher level:

1) Async keyword enables the await and that’s all it does. Async keyword does not run the method in a separate thread. The beginning f async method runs synchronously until it hits await on a time-consuming task.

2) You can await on a method that returns Task or Task of type T. You cannot await on async void method.

3) The moment main thread encounters await on time-consuming task or when the actual work is started, the main thread returns to the caller of the current method.

4) If the main thread sees await on a task that is still executing, it doesn’t wait for it and returns to the caller of the current method. In this way, the application remains responsive.

6) When this await task is completed, all the code below it will be executed by the separate thread

Below is the sample code. Execute it and check the thread id

using System;

namespace AsyncAwaitDemo
{
class Program
{
public static async void AsynchronousOperation()
{
int count = await AsyncMethod();

DependentMethod(count);

}

{
int count = 0;

{
count = 10;
});

return count;
}

public static void DependentMethod(int count)
{
}

static void Main(string[] args)
{

AsynchronousOperation();

}

}
}



1 people think this answer is useful

is using them equal to spawning background threads to perform long duration logic?

This article MDSN:Asynchronous Programming with async and await (C#) explains it explicitly:

The async and await keywords don’t cause additional threads to be created. Async methods don’t require multithreading because an async method doesn’t run on its own thread. The method runs on the current synchronization context and uses time on the thread only when the method is active.

1 people think this answer is useful

Below is code which reads excel file by opening dialog and then uses async and wait to run asynchronous the code which reads one by one line from excel and binds to grid

namespace EmailBillingRates
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
lblProcessing.Text = "";
}

private async void btnReadExcel_Click(object sender, EventArgs e)
{
string filename = OpenFileDialog();

Microsoft.Office.Interop.Excel.Application xlApp = new Microsoft.Office.Interop.Excel.Application();
Microsoft.Office.Interop.Excel.Workbook xlWorkbook = xlApp.Workbooks.Open(filename);
Microsoft.Office.Interop.Excel._Worksheet xlWorksheet = xlWorkbook.Sheets[1];
Microsoft.Office.Interop.Excel.Range xlRange = xlWorksheet.UsedRange;
try
{

}
catch (Exception ex)
{
MessageBox.Show(ex.Message.ToString());
}
finally
{
//cleanup
// GC.Collect();
//GC.WaitForPendingFinalizers();

//rule of thumb for releasing com objects:
//  never use two dots, all COM objects must be referenced and released individually

//release com objects to fully kill excel process from running in the background
Marshal.ReleaseComObject(xlRange);
Marshal.ReleaseComObject(xlWorksheet);

//close and release
xlWorkbook.Close();
Marshal.ReleaseComObject(xlWorkbook);

//quit and release
xlApp.Quit();
Marshal.ReleaseComObject(xlApp);
}

}

private void btnSendEmail_Click(object sender, EventArgs e)
{

}

private string OpenFileDialog()
{
string filename = "";
OpenFileDialog fdlg = new OpenFileDialog();
fdlg.Title = "Excel File Dialog";
fdlg.InitialDirectory = @"c:\";
fdlg.Filter = "All files (*.*)|*.*|All files (*.*)|*.*";
fdlg.FilterIndex = 2;
fdlg.RestoreDirectory = true;
if (fdlg.ShowDialog() == DialogResult.OK)
{
filename = fdlg.FileName;
}
return filename;
}

{
lblProcessing.Text = "Processing File.. Please wait";
int rowCount = xlRange.Rows.Count;
int colCount = xlRange.Columns.Count;

// dt.Column = colCount;
dataGridView1.ColumnCount = colCount;
dataGridView1.RowCount = rowCount;

for (int i = 1; i <= rowCount; i++)
{
for (int j = 1; j <= colCount; j++)
{
//write the value to the Grid
if (xlRange.Cells[i, j] != null &amp;&amp; xlRange.Cells[i, j].Value2 != null)
{
dataGridView1.Rows[i - 1].Cells[j - 1].Value =  xlRange.Cells[i, j].Value2.ToString();
}

}
}
lblProcessing.Text = "";
return 0;
}
}

internal class async
{
}
}



0 people think this answer is useful

The answers here are useful as a general guidance about await/async. They also contain some detail about how await/async is wired. I would like to share some practical experience with you that you should know before using this design pattern.

The term “await” is literal, so whatever thread you call it on will wait for the result of the method before continuing. On the foreground thread, this is a disaster. The foreground thread carries the burden of constructing your app, including views, view models, initial animations, and whatever else you have boot-strapped with those elements. So when you await the foreground thread, you stop the app. The user waits and waits when nothing appears to happen. This provides a negative user experience.

You can certainly await a background thread using a variety of means:

Device.BeginInvokeOnMainThread(async () => { await AnyAwaitableMethod(); });

// Notice that we do not await the following call,
// as that would tie it to the foreground thread.
try
{
Task.Run(async () => { await AnyAwaitableMethod(); });
}
catch
{}



The complete code for these remarks is at https://github.com/marcusts/xamarin-forms-annoyances. See the solution called AwaitAsyncAntipattern.sln.

The GitHub site also provides links to a more detailed discussion on this topic.

-1 people think this answer is useful

Tasks let you control the number of threads you are running on.
The optimal number of threads is the number of cores you have.

• when your app is Console, WinForms or WPF then you are normally running on a single-thread.

• in this case you want to increase the number of threads
• your main tool is Task.Run(), and sometimes Parallel.ForERach()
• doing synchronous I/O on a thread (with Task.Run()) is sub-optimal but acceptable
• when your app runs on a Webserver it normally is running on (too) many threads.
asp.net waits for incoming requests and quickly hands each one to a new pool thread.

• in this case you want to decrease the number of threads
• your main tool is to await asynchrous I/O
• make sure you have an unbroken await chain from your async Action method down to the actual I/O
• doing synchronous I/O or CPU intensive work on a thread (with Task.Run()) is a de-optimization.