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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...