When waiting for Tasks using Task.WaitAll and specifying a timeout if the WaitAll times out do I also have to separately observe any unfinished tasks (e.g. by registering a continuation)?
Consider the following C# code: CancellationTokenSource tCancelSource = new CancellationTokenSource();
Suppose I have an API that returns a Task as an object: private static object CreateTask() { return Task.Factory.StartNew(() => \"Task string\");
I need to traverse a tree quickly, and I would like to do it in parallel. I\'d rather use the parallel extensions than manually spin up a bunch of threads.
Here\'s the situation, I am writing the framework for a code war contest. As the code runs, for each turn, it calls a method in the library provided by each contestant. The rules of the contest is the
I have come across a situation where Tasks I am creating only seem to work when I am debugging the code.
I want to download a web site with the WebBrowser Control (WPF) in the Background and parse the site afterwards. The download should be in a "tight loop\". I only need the source as a string. I t
The class CancellationTokenSource is disposable. A quick look in Reflector proves usage of KernelEvent, a (very likely) unmanaged resource.
This is all happening in a windows service. I have a Queue<T> (actually a ConcurrentQueue<T>) holding items waiting to be processed. But, I don\'t want to process only one at a time, I wa
I have a simulation that generates data which must be saved to database. ParallelLoopResult res = Parallel.For(0, 1000000, options, (r, state) =>