https://www.dotnetzone.gr:443/cs/blogs/kbadas/archive/2014/02/16/asynchronous-programming-in-net-4-5.aspxAsynchronous programming has been a part of Microsoft's applications for a long time. However things tend to mature. .NET 4.5, released in August 2012, brought up C# 5 and VB 2012. And along came a new way of creating asynchronous methods. Instead ofelCommunityServer 2.1 SP3 (Build: 20423.1)https://www.dotnetzone.gr:443/cs/blogs/kbadas/archive/2014/02/16/asynchronous-programming-in-net-4-5.aspx#75053Tue, 18 Feb 2014 22:51:19 GMT2622095e-976c-431a-859e-16783ec7ecd7:75053Παναγιώτης Καναβός<p>You should refrain from using `async void` in general, unless you are trying to create an asynchronous event handler. `async void` methods are essentially fire and forget, they can't be awaited and you can't check whether they failed or not. &nbsp;In ASP.NET especially, you should use Page.RegisterAsyncTask if you want to execute a Task asynchronously. Scott Hanselman has an article describing exactly this case at <a rel="nofollow" target="_new" href="http://www.hanselman.com/blog/TheMagicOfUsingAsynchronousMethodsInASPNET45PlusAnImportantGotcha.aspx">http://www.hanselman.com/blog/TheMagicOfUsingAsynchronousMethodsInASPNET45PlusAnImportantGotcha.aspx</a></p> https://www.dotnetzone.gr:443/cs/blogs/kbadas/archive/2014/02/16/asynchronous-programming-in-net-4-5.aspx#75055Wed, 19 Feb 2014 06:56:02 GMT2622095e-976c-431a-859e-16783ec7ecd7:75055k badas<p>You are quite right. I admit I hadn't heard of the &nbsp;problems that might arise from the combination of async and void. I've changed the parts of the article that made use of it. Thanks for the info.</p>