ConfigureAwait behavior in C Sharp (C#) - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of ConfigureAwait(false) in async method

What will be the output of this C# program?

using System;
using System.Threading.Tasks;

class Program
{
    static async Task Main()
    {
        Console.WriteLine($"Start Thread: {Environment.CurrentManagedThreadId}");
        await Task.Delay(100).ConfigureAwait(false);
        Console.WriteLine($"After await Thread: {Environment.CurrentManagedThreadId}");
    }
}

C Sharp (C#)

using System;
using System.Threading.Tasks;

class Program
{
    static async Task Main()
    {
        Console.WriteLine($"Start Thread: {Environment.CurrentManagedThreadId}");
        await Task.Delay(100).ConfigureAwait(false);
        Console.WriteLine($"After await Thread: {Environment.CurrentManagedThreadId}");
    }
}

A Start Thread: 1\nAfter await Thread: 3

B Start Thread: 3\nAfter await Thread: 3

C Start Thread: 1\nAfter await Thread: 1

D Start Thread: 3\nAfter await Thread: 1

💡 Hint

Think about how ConfigureAwait(false) affects thread continuation.

ConfigureAwait(false) tells the await to not capture the current synchronization context. This means the continuation after await may run on a different thread, often a thread pool thread, not necessarily the original thread.

❓ Predict Output

intermediate

Effect of ConfigureAwait(true) on UI thread

Consider a UI application where the main thread ID is 1. What will this code print?

using System;
using System.Threading.Tasks;

class Program
{
    static async Task Main()
    {
        Console.WriteLine($"Before await Thread: {Environment.CurrentManagedThreadId}");
        await Task.Delay(50).ConfigureAwait(true);
        Console.WriteLine($"After await Thread: {Environment.CurrentManagedThreadId}");
    }
}

C Sharp (C#)

using System;
using System.Threading.Tasks;

class Program
{
    static async Task Main()
    {
        Console.WriteLine($"Before await Thread: {Environment.CurrentManagedThreadId}");
        await Task.Delay(50).ConfigureAwait(true);
        Console.WriteLine($"After await Thread: {Environment.CurrentManagedThreadId}");
    }
}

A Before await Thread: 2\nAfter await Thread: 1

B Before await Thread: 1\nAfter await Thread: 2

C Before await Thread: 2\nAfter await Thread: 2

D Before await Thread: 1\nAfter await Thread: 1

💡 Hint

ConfigureAwait(true) captures the synchronization context.

With ConfigureAwait(true), the continuation after await runs on the original context (UI thread), so thread ID remains the same.

🔧 Debug

advanced

Identify the error caused by missing ConfigureAwait(false)

What problem can occur in this code snippet when ConfigureAwait(false) is not used?

public async Task LoadDataAsync()
{
    await Task.Delay(1000); // Simulate data loading
    UpdateUI();
}

void UpdateUI()
{
    // Update UI elements here
}

C Sharp (C#)

public async Task LoadDataAsync()
{
    await Task.Delay(1000); // Simulate data loading
    UpdateUI();
}

void UpdateUI()
{
    // Update UI elements here
}

A No error; code runs fine on UI thread.

B Deadlock due to blocking on async call.

C InvalidOperationException because UpdateUI runs on non-UI thread.

D Compile-time error due to missing ConfigureAwait.

💡 Hint

Think about thread affinity for UI updates.

Without ConfigureAwait(false), the continuation tries to resume on the captured context. But if the context is lost or the method is called from a non-UI thread, UpdateUI may run on a wrong thread causing an InvalidOperationException.

📝 Syntax

advanced

Correct usage of ConfigureAwait in async method

Which of the following code snippets correctly uses ConfigureAwait to avoid capturing the synchronization context?

A await SomeAsyncMethod.ConfigureAwait(false);

B await SomeAsyncMethod().ConfigureAwait(false);

C await SomeAsyncMethod().ConfigureAwait();

D await ConfigureAwait(false).SomeAsyncMethod();

💡 Hint

Remember ConfigureAwait is called on the task returned by the async method.

ConfigureAwait is an extension method on Task or Task<T> and must be called on the awaited task instance.

🚀 Application

expert

Choosing ConfigureAwait usage in library code

You are writing a library method that performs asynchronous work. The library should not assume the caller's synchronization context. Which ConfigureAwait usage is best practice inside your library method?

A Always use ConfigureAwait(false) to avoid capturing context.

B Always use ConfigureAwait(true) to capture context for caller.

C Do not use ConfigureAwait at all and let caller decide.

D Use ConfigureAwait(false) only if caller passes a flag.

💡 Hint

Think about library code independence from UI or synchronization contexts.

Library code should avoid capturing synchronization context to prevent deadlocks and improve performance. Using ConfigureAwait(false) is recommended.