Tasks are (still) not threads and async is not parallel

Pam Lahoud

Premier Developer consultant Ben Williams recently had the honor of having one of his blog posts reposted to Wintellect’s Dev Center as a guest post.  Here’s a blurb from that post, be sure to head over to Ben’s blog to check out the full technical deep-dive and download his sample WPF application.

I talk to a lot of developers who are either new to .NET or are moving from an older version to the newer platform and tools. As such I’m always trying to think of new ways to describe the nature of Tasks vs Threads and async vs parallel. Modern .NET development is steeped in the async/await model and async/await is built on the Task model. So understanding these concepts is key to long term success building apps in .NET.

In order to help visualize this I built a simple WPF application that displays a chart of an application’s activity. I want to display some of the potential variations in behavior of what appear to be a simple set of async tasks.

You can read the full text of the article here:



Discussion is closed.

Feedback usabilla icon