C# 5.0 mostly bluff about the asynchronous programming. Of course it has some really kick ass features in the asynchronous programming world.
First of all, asynchronous programing is not new in C# 5.0. It’s been there from C# 1.0, so what’s the big deal now ?
In C# 5.0 they have created a whole new, very tidy and easy programing approach in asynchronous programing. It’s really very tidy.
Here’s a WPF sample application which downloads the headers of an HTTP request and displays in a TextBox. Simply we all know that if we do this without threads our UI will hang until the download operation completes. The solution we’ve been using is threading.
Here I want to make a point; conceptually we all know that using the threads for the above problem will yield the solution for UI unresponsiveness. But it creates challenges like monitoring the threads and updating the UI, handling exceptions and code untidiness.
Again one more point, when using the threads for the above problem .NET provides various solutions. In Win Forms using the BackgroundWorker is the popular way, in WPF we go for the Dispatcher, we also have our same old IAsyncCallback and delegates mechanism, using the thread pool explicitly, creating and customizing our own threads.
As you see, almost all the above methods are cluttered every where, developers use their own way to handle the problem, not bad but it’s not good either.
And also we have our problems in updating the UI; especially when updating a UI control from a different thread. We get the Cross thread access exceptions.
Here’s the code that shows one way of how the above scenario can be implemented prior to C# 5.0 in WPF.
private void OldAsyncTechnique()
SynchronizationContext sync = SynchronizationContext.Current;
var req = (HttpWebRequest)WebRequest.Create("https://thuruinhttp.wordpress.com");
req.Method = "HEAD";
var resp = (HttpWebResponse)req.EndGetResponse(asyncResult);
TxtHeaders.Text = FormatHeaders(resp.Headers);
Here I get the SynchronizationContext of the current thread, (means the main UI thread) and creates my web request. Then I call the asynchronous BeginGetResponse method of the HttpWebRequest class.
To make the code compact, I called the EndGetResponse in lamda. Using the SynchronizationContext of the UI thread I post the message to the UI control.
But this very complex and I have to pass state object parameters and all. (I have passed null here).
Note : This is not the only way to do this.
In C# 5.0 we have new keywords async and await. (You still can enable this in .NET 4 by installing the Async CTP, but since the VS 2012 and .NET 4.5 is released do not waste your time on doing this. You can simply upgrade yourself to .NET 4.5 world)
Here’s the code.
private async void NewMethod()
HttpWebRequest req = (HttpWebRequest)HttpWebRequest.Create("https://thuruinhttp.wordpress.com");
req.Method = "HEAD";
HttpWebResponse res = (HttpWebResponse) await req.GetResponseAsync();
TxtHeaders.Text = FormatHeaders(res.Headers);
Simple as that. You declare the method async and make an awaitable type.
When the code hits the await keyword the method returns immediately, and once the await got the results, the method begins the execution from where it left. Simple theory.
But how it is possible, again that is simple inside C# when you compile the above code, C# compiler rewrites the above code in a fine and an efficient old way.
The real working pattern and how things happen are complex and it used the TPL heavily.
Important : Once you install .NET 4.5 you will get the GetResponseAsync() in the WebClient class. And most classes are enriched with these types of async methods in .NET 4.5. We can have our async and await functionality in our custom classed as well.
Here’s the implementation of the FormatHeaders method.
private string FormatHeaders(WebHeaderCollection collection)
StringBuilder builder = new StringBuilder();
foreach (var s in collection.Keys)
builder.Append(s + " : ");