I just blogged about it here: CancellationToken and Thread.Sleep in Short: var cancelled = token.WaitHandle.WaitOne(TimeSpan.FromSeconds(5)); In your context: void MyFunc (CancellationToken ct) { //… // simulate some long lasting operation that should be cancelable var cancelled = ct.WaitHandle.WaitOne(TimeSpan.FromSeconds(10)); }
But what if my action is not lambda but a method placed in other class and I don’t have direct access to token? Is the only way is to pass token as state? Yes, in that case, you would need to pass the token boxed as state, or included in some other type you use … Read more
CancellationToken.Register returns a CancellationTokenRegistration instance. If you call Dispose on that instance, your registration will be removed.
After filing an issue with corefx, the documentation remarks have been updated to make this a guaranteed feature: You can also use the C# default(CancellationToken) statement to create an empty cancellation token.
You are passing the cancellation token as the parameter object; that won’t work. The first async methods in dapper did not expose a cancellation token; when I tried to add them as an optional parameter (as a separate overload, to avoid breaking existing assemblies), things got very confused with “ambiguous method” compilation problems. Consequently, I … Read more
You can implement your work method as follows: private static void Work(CancellationToken cancelToken) { while (true) { if(cancelToken.IsCancellationRequested) { return; } Console.Write(“345”); } } That’s it. You always need to handle cancellation by yourself – exit from method when it is appropriate time to exit (so that your work and data is in consistent state) … Read more
I finally found a workaround. Combine the async call with a delay task (Task.Delay) using Task.WaitAny. When the delay elapses before the io task, close the stream. This will force the task to stop. You should handle the async exception on the io task correctly. And you should add a continuation task for both the … Read more
If the steps are somehow independend regarding the dataflow within the method, but can’t be executed in a parallel matter, the following approach may be better readable: void Run() { // list of actions, defines the order of execution var actions = new List<Action<CancellationToken>>() { ct => Step1(ct), ct => Step2(ct), ct => Step3(ct) }; … Read more
You should use it. Right now it only applies if you have an AsyncTimeout, but it’s likely that a future MVC/WebAPI version will interpret the token as “either timeout or the client disconnected”.
Cancellation in Managed Threads: Cancellation is cooperative and is not forced on the listener. The listener determines how to gracefully terminate in response to a cancellation request. You didn’t write any code inside your Task.Run method to access your CancellationToken and to implement cancellation – so you effectively ignored the request for cancellation and ran … Read more