I have a WPF (C# and .NET 4) application that has a long running task in it that blocked the UI giving the impression that it has hung. I decided to put this long-running task onto a separate thread b
I\'m having trouble taking a subject of public Subject<IEnumerable<Person>> PersonDataSubject;
Any tips on how I can optimize below further using TPL and/or PLINQ. Below code runs on a background worker
I have a queue onto which pending fourier transform requests (comparatively time consuming operations) are placed - we could get thousands of transform requests per second in some cases, so its gotta
I have the following method that are called sequentially: private StringBuilder ReadPDF(); private StringBuilder CleanText(StringBuilder sb);
I have to run about 150 tasks. Right 开发者_StackOverflownow the app is using only 25 threads per core and I need that to be a higher number. Is it possible to increase that limit ?The only way to con
Task.Factory.StartNew() basically receives an Action and 开发者_如何学Creturns a Task. In The Async CTP we have TaskEx.Run() which also receives an Action and returns a Task. They seem to do that same
I have a set of nicely structured objects set up along these lines: abstract class Data { public abstract void GetData();
What is the difference between Task.WaitAll() and Task开发者_StackOverflow社区.WhenAll() from the Async CTP?
This question already has answers here: Closed 10 years ago. Possible Duplicate: Retry a task multiple times based on user input in case of an exception in task
加载中,请稍侯......