Skip to main content

What is the behavior of an async method that returns void

In .NET 4.5 running async code was made easier than ever with async. I already talk a little about this new functionality, but I felt need to talk a little bit about some asycn methods that returns Task or (Task) and the async methods that returns void.
If we have an async method with the following definition:
public async Task<string> DoSomeActionAsync(…) { … }
In this case this method can be executed async and the method can be awaited. The user can wait until the action is executed. After the action is executed, the control is given back to code that waited the action to end. This action can start delegate asynchronous work.
In contrast with this definition, if we have the following definition:
public async void DoSomeActionAsync (…) { … }
This action cannot be awaited. When the user calls this method is a call of type fire and forget. The code that made the call will not be notified when the action was finished. Because of this, each call of this type start a separate independent flow.
Usually, an async method returns void when we want to define an event handler or to override void methods. Using this syntax it is very easy to call from event handler async methods.When you want to define a library that executes async calls or to define some helper methods you should always return Task or Task.
Also, when you work with async methods don’t forget to start them as soon as possible. I saw some async code, where the user defined some async methods and only at the end of an action he begins to execute these actions. If you have the possibility to start an async action sooner, than do it. In this you can reduce the execution time of your action. Because you can wait an async method multiple times, nothing will happen if you try to wait more than one time an action.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.