We’re happy to announce that you can now download an Async Targeting Pack for Visual Studio 11 that lets you target .NET 4 and Silverlight 5. The included DLLs address the previously discussed issue of the Visual Studio 11 Beta compilers being incompatible with the AsyncCtpLibrary* DLLs from the Async CTP;
Over on the Windows 8 app developer blog, I’ve written a blog post about using await with WinRT. I hope you enjoy it!
In a previous post Should I expose asynchronous wrappers for synchronous methods?, I discussed “async over sync,” the notion of using synchronous functionality asynchronously and the benefits that doing so may or may not yield. The other direction of “sync over async”
From time to time, I receive questions from developers which highlight either a need for more information about the new “async” and “await” keywords in C# and Visual Basic. I’ve been cataloguing these questions, and I thought I’d take this opportunity to share my answers to them.
Developers familiar with parallel programming are also familiar with a wide range of potential problems that can occur when practicing the art. One of the most well-known issues is “deadlock,” where two or more operations are waiting on each other to complete in a manner such that none of them will be able to complete.
In .NET 4.5 Beta, the Stream class provides multiple virtual methods related to reading and writing:
Read, BeginRead / EndRead, ReadAsync
Write, BeginWrite / EndWrite, WriteAsync
As a developer deriving from Stream, it’s helpful to understand what the base implementations do and when you can and should override them.