How To Write Bulletproof Multi-Threaded C# Code

This course teaches you how to write robust multi-threaded C# code. A skill every professional .NET developer must know

Updated on May 18, 2015. Launched the course.

BEST COURSE CHOICE for beginners and intermediate C# developers who want to learn how to write unbreakable multi-threaded code, and take their programming skills to the next level.

Do you know how to write robust multi-threaded C# code that does not crash?

Yeah, I thought I did too. In 2005 I built an RFID-enabled supermarket shelf and wrote some multi-threaded C# code to ping the antennas and automatically detect groceries fitted with an RFID tag.

The result? The program was very unstable and crashed many times. My client did eventually manage to perform a successful demo, but it required a lot of reboots.

Why was my code so unstable? Because I had forgotten to put critical sections around some of the variables that were shared between threads.

Writing multi-threaded code is hard. The sobering truth is that, unless you know exactly what you’re doing, your code is pretty much guaranteed to crash in production.

Don’t let this happen to you!

It doesn’t have to be like this. If you have a good understanding of multi-threaded programming and follow a few simple industry best practices, you can write robust code that can take a beating.

I wrote a multi-threaded conversion utility a few months ago, that successfully migrated 100,000 documents from SharePoint 2010 to SharePoint 2013. The program worked flawlessly the first time, because I implemented all of the best practices for writing asynchronous C# code.

Sound good?

In this course I am going to share these practices with you.

In a series of short lectures I will cover many multi-threading topics. I will show you all of the problems you can expect in asynchronous code, like race conditions, deadlocks, livelocks and synchronisation issues. I’ll show you quick and easy strategies to resolve these problems.

By the end of this course you will be able to write robust multi-threaded C# code that can take a beating.