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.

Comments

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.

Coding

Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms

Programming

Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming

Design

Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…