async-ctp

I am using the Async CTP library for Windows Phone. Does anyone know how to cancel a pending webrequest? Request = (HttpWebRequest)WebRequest.Create(url); Request.Credentials = new NetworkCredential(_settings.Username, _settings.Password); WebResponse resp; try { resp = await Request.GetResponseAsync(); } There is no cancellation token (as specified in the ASYNC Ctp tap document ). You could try calling Request.Abort() . 来源： https://stackoverflow.com/questions/8635723/cancel-an-async-webrequest

There are many reasons to put a token in the constructor of a task, mentioned here: Cancellation token in Task constructor: why? With the use of keywords, async / await, how is that working? for example my code below: public async Task MethodAsync(CancellationToken token) { await Method01Async(); await Method02Async(); } Although it is an asynchronous process. In no time I used "Task.StartNext" or "Task.Run" or "new Task". To be able to specify my cancellation token, how can I do? You aren't supposed to use the Task constructor in async methods. Usually, you just want to pass the

Is it bad to have expensive code at the start of an async method, before the first await is called? Should this code be wrapped with a TaskEx.Run instead? public async Task Foo() { // Do some initial expensive stuff. // ... // First call to an async method with await. await DoSomethingAsync; } As Reed says, it really depends on the context. The code has to run at some point - but depending on the context, it may end up being run on a thread pool thread instead of some critical one. Rather than using Task.Run , I'd use TaskEx.Yield : public async Task Foo() { await TaskEx.Yield(); // Do

I want to add async support to current VS 2010 .NET 4.0 C# project I have found: Visual Studio Async CTP - http://www.microsoft.com/en-us/download/details.aspx?id=9983 Microsoft.Bcl.Async - https://nuget.org/packages/Microsoft.Bcl.Async I don't even get real difference between them. I installed both. Visual Studio Async CTP (Version 3), Microsoft.Bcl and Microsoft.Bcl.Async. (also used to run tools\portable-net40+sl4+win8+wp71\install.ps1 in Microsoft.Bcl) And still can't see any effect. Same error for public async Task<CommResponse> -> Error 37 The type or namespace name 'async' could not be

I'm converting some async/await code to chained tasks, so I can use it in the released framework. The await code looks like this public async Task<TraumMessage> Get() { var message = await Invoke("GET"); var memorized = await message.Memorize(); return memorized; } where Task<TraumMessage> Invoke(string verb) {} Task<TraumMessage> Memorize() {} I was hoping to chain Invoke and Memorize to return the task produced by Memorize , but that results in a Task<Task<TraumMessage> . The solution i've ended up is a TaskCompletionSource<TraumMessage> as my signal: public Task<TraumMessage> Get() { var

I've been reading about the new async await keyword and it sounds awesome, but there is one key question I haven't been able to find the answer for in any of the intro videos I've watched so far (I also read the whitepaper a while back). Suppose I have a call to await in a nested function on the main UI thread. What happens to the thread at this point? Does control go back to the message loop and the UI thread is free to process other inputs? When the awaited task completes, does the entire stack get pushed onto a message queue, such that control will return through each of those nested