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 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&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…