c#-5.0

I'd like to make a function async, so I simply add async like this: public async static void something(){ } You can see that its return-type is void . I just want this function to be called asynchronously without blocking, since return is void so no await is needed. But Visual Studio 2012 just cannot compile this, it says that I miss await ? Could you please advise a sample that makes a function async without using await . I think that maybe you misunderstand what async does. The warning is exactly right: if you mark your method async but don't use await anywhere, then your method won't be

Trying to understanding the difference between the TPL & async / await when it comes to thread creation. I believe the TPL ( TaskFactory.StartNew ) works similar to ThreadPool.QueueUserWorkItem in that it queues up work on a thread in the thread pool. That's of course unless you use TaskCreationOptions.LongRunning which creates a new thread. I thought async / await would work similarly so essentially: TPL: Factory.StartNew( () => DoSomeAsyncWork() ) .ContinueWith( (antecedent) => { DoSomeWorkAfter(); },TaskScheduler.FromCurrentSynchronizationContext()); Async / Await : await DoSomeAsyncWork();

Everywhere I read it says the following code should work, but it doesn't. public async Task DoSomething(int x) { try { // Asynchronous implementation. await Task.Run(() => { throw new Exception(); x++; }); } catch (Exception ex) { // Handle exceptions ? } } That said, I'm not catching anything and get an "unhandled exception" originating at the 'throw' line. I'm clueless here. You have the "Just my code" Option turned on. With this on, it is considering the exception unhandled with respect to "just your code"--because other code is catching the exception and stuffing it inside of a Task, later

The MSDN documentation appears to state that async and await are suitable for IO-bound tasks whereas Task.Run should be used for CPU-bound tasks. I'm working on an application that performs HTTP requests to retrieve HTML documents, which it then parses. I have a method that looks like this: public async Task<HtmlDocument> LoadPage(Uri address) { using (var httpResponse = await new HttpClient().GetAsync(address)) //IO-bound using (var responseContent = httpResponse.Content) using (var contentStream = await responseContent.ReadAsStreamAsync()) return await Task.Run(() => LoadHtmlDocument

Two new keywords added to the C# 5.0 language are async and await , both of which work hand in hand to run a C# method asynchronously without blocking the calling thread. My question is, do these methods actually take advantage of multiple cores and run in parallel or does the async method run in the same thread core as the caller? Two new keywords added to the C# 5.0 language are async and await, both of which work hand in hand to run a C# method asynchronously without blocking the calling thread. That gets across the purpose of the feature, but it gives too much "credit" to the async/await