Skip to main content

Different methods to cancel a Task

From .NET 4.0, Task’s made our life easier. In comparison with threads, it is much simple to start a new thread execution. Because of this, you can create Task pretty simple, but when you want to make more complex things, you end up with a big headache.
In this post we will see how we should cancel a Task. Creating a task it is pretty simple thing:
Task task = new Tasl(()=> { Console.WriteLine(“New Task”); } );
But how we can cancel a task? To be able to cancel a task we need to use a cancellation token. Using this kind of object we will be able to transmit the cancelation request to our task. Don’t forget that you can use a cancellation token instance only once. This means that we cannot reuse the cancelation tokens more than once.
The task constructor accepts as second parameter a cancelation token. This token can be used in our task when we are in a point when we want to check if our task was cancelled. There are different methods to detect if the current task was cancelled or not.
The simplest way to check if our task was cancelled or not is with ThrowIfCancellationRequested method of CacellationToken. If our task was cancelled, than this method will throw an OperationCanceledException. Be aware that you should not cache this exception in your task. This exception should be catch in the code that call Wait method.
CancellationToken cancellationToken = cancellationTokenSource.Token;
…
cancellationToken.ThrowIfCancellationRequested();
Another way to check if a task was cancelled or not is by checking IsCancellationRquested property of CancellationToken. This property will return true if the task was cancelled. Like in the first option, if we have an infinite loop, we should stop it (this needs to be done from our code) – it will not be made automatically.
if (cancellationToken.IsCancellationRquested)
{
  // do custom action that needs to be done when the task is cancelled
}
There also cases when we cannot have this kind of checks in our code. For example if we call long running methods from external components. In this case we can register to an event of CancellationToken that will be called when our task is cancelled. In this event callback we can do any kind of action to cancel our task.
cancellationToken.Register( () =>
{
  // do custom action that needs to be done to cancel our task
});
When you create a new task, the CancellationToken instance can be obtained pretty easy from CancellationTokenSource. This is used to signal a cancellation action. Be aware of one important thing. If you wait a task with Wait method, than you should surround this call with a try cache. The OperationCanceledException exception needs to be catch. This method is thrown every time when a task is cancelled and ThrowIfCancellationRequested is used.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too