Stephen Toub: Async Update - Technical Overview and Building Awaitable Types
- Posted: Apr 15, 2011 at 8:40 AM
- 59,478 Views
- 4 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
The recent Visual Studio Async CTP SP1 refresh includes many core improvements, bug fixes and new support for WP7 and VS Express. Architect Stephen Toub digs into some of the updates and explains how making your own awaitable types has gotten easier in this release. As usual, Stephen covers a lot of technical ground and shares his knowledge and insights very clearly. Tune in.
Get the latest Async CTP: http://msdn.microsoft.com/en-US/vstudio/async
Provide feedback/ask questions: http://social.msdn.microsoft.com/Forums/en-US/async/threads
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
nice. and Lucian Wischik is posting a serials of blog posts about this in details too
http://blogs.msdn.com/b/lucian/archive/2011/04/15/async-ctp-refresh-design-changes.aspx
@felix9: Lucian will also show up on C9 very soon covering compiler changes and more.
C
I tend to think that so-called fluent APIs are sometimes abused, but it seems to me that something like
would be more readable and a more flexible pattern for dealing with future unknowns.
I just realized the trusty DoEvents() was sort of an old school version of async. Schedule rest of me on the queue on current context.
Good work. Look forward to trying the new bits. Thank you.
Remove this comment
Remove this thread
close