How async execution flows in C Sharp (C#) - Quick Revision & Summary

Recall & Review

beginner

What does the 'async' keyword do in C#?

The 'async' keyword marks a method as asynchronous, allowing it to run operations without blocking the main thread and enabling the use of 'await' inside it.

beginner

What is the role of the 'await' keyword in async methods?

'await' pauses the execution of the async method until the awaited task completes, then resumes execution without blocking the thread.

beginner

How does async execution flow affect the main thread?

Async execution allows the main thread to continue running other code while waiting for asynchronous operations to complete, improving responsiveness.

intermediate

What happens when an async method reaches an 'await' statement?

When an async method reaches 'await', it returns control to the caller and schedules the rest of the method to continue after the awaited task finishes.

beginner

Explain the difference between synchronous and asynchronous execution flow.

Synchronous execution runs tasks one after another, blocking the thread until each finishes. Asynchronous execution allows tasks to run without blocking, letting the program do other work while waiting.

What does the 'async' keyword enable in a C# method?

A Allows the method to run without blocking and use 'await'

B Makes the method run faster synchronously

C Prevents the method from returning a value

D Disables exception handling inside the method

'async' allows the method to run asynchronously and use 'await' to pause without blocking.

What happens when 'await' is used on a Task in an async method?

A The method pauses and the thread is blocked

B The method runs synchronously without pausing

C The method pauses but the thread is free to do other work

D The method throws an exception immediately

'await' pauses the method but frees the thread to continue other work.

Which statement best describes async execution flow?

A Tasks run one after another, blocking the thread

B Tasks run without blocking, allowing other code to run

C Tasks run only on background threads

D Tasks run only after the main thread finishes

Async execution allows tasks to run without blocking, so other code can continue.

When an async method hits an 'await', what does it do?

A Throws a runtime error

B Blocks the thread until the task completes

C Immediately completes the method

D Returns control to the caller and resumes later

The method returns control and resumes after the awaited task finishes.

Why is async execution useful in UI applications?

A It keeps the UI responsive during long operations

B It makes the UI freeze while waiting

C It disables user input

D It slows down the application

Async execution keeps the UI responsive by not blocking the main thread.

Describe how the flow of execution changes when using async and await in C#.

Think about what happens when the method reaches 'await' and how the thread behaves.

Explain why async execution improves application responsiveness, especially in UI apps.

Consider what happens if the main thread is blocked during a long task.

Practice

1. What does the await keyword do in an async method in C#?

easy

A. It immediately blocks the thread until the awaited task completes.

B. It converts a synchronous method into an asynchronous one automatically.

C. It pauses the method until the awaited task completes without blocking the thread.

D. It cancels the running async method.

Solution

1. Step 1: Understand the role of await

   The await keyword pauses the async method execution until the awaited task finishes, but it does not block the thread, allowing other work to continue.

2. Step 2: Differentiate from blocking

   Blocking the thread would freeze the program, but await allows the thread to be free for other tasks.

3. Final Answer:

   It pauses the method until the awaited task completes without blocking the thread. -> Option C

4. Quick Check:

   await pauses without blocking [OK]

Hint: Remember: await pauses method but frees thread [OK]

Common Mistakes:

• Thinking await blocks the thread
• Confusing await with async keyword
• Assuming await cancels tasks

2. Which of the following is the correct syntax to declare an asynchronous method in C#?

easy

A. public async void MyMethod() { }

B. public void async MyMethod() { }

C. async public void MyMethod() { }

D. public void MyMethod async() { }

Solution

1. Step 1: Identify correct async method declaration

   The correct syntax places the async keyword before the return type: public async void MyMethod().

2. Step 2: Check other options for syntax errors

   Options A, B, and D have incorrect keyword order or placement, which causes syntax errors.

3. Final Answer:

   public async void MyMethod() { } -> Option A

4. Quick Check:

   async keyword before return type [OK]

Hint: Put async before return type in method declaration [OK]

Common Mistakes:

• Placing async after return type
• Using async as a method modifier incorrectly
• Adding parentheses after async

3. What will be the output of the following C# code?

async Task<int> GetNumberAsync() {
    await Task.Delay(100);
    return 5;
}

async Task MainAsync() {
    var task = GetNumberAsync();
    Console.WriteLine("Before await");
    int result = await task;
    Console.WriteLine($"Result: {result}");
}

MainAsync().Wait();

medium

A. No output due to deadlock

B. Before await\nResult: 5

C. Before await

D. Result: 5\nBefore await

Solution

1. Step 1: Analyze the order of execution

   The method prints "Before await" immediately after starting the async task, then awaits the task completion before printing the result.

2. Step 2: Understand await behavior

   Await pauses MainAsync until GetNumberAsync completes, then prints "Result: 5".

3. Final Answer:

   Before await\nResult: 5 -> Option B

4. Quick Check:

   Print before await, then after task completes [OK]

Hint: Output before await prints first, then awaited result [OK]

Common Mistakes:

• Assuming result prints before 'Before await'
• Thinking await blocks main thread
• Expecting no output due to deadlock

4. Identify the problem in this async code snippet:

async Task<int> CalculateAsync() {
    Task.Delay(1000);
    return 10;
}

medium

A. Method should not be async if it returns a value.

B. Return type should be void, not Task<int>.

C. Task.Delay cannot be used inside async methods.

D. Missing await before Task.Delay, so delay is ignored.

Solution

1. Step 1: Check usage of Task.Delay

   The method calls Task.Delay(1000) but does not await it, so the delay runs but the method immediately returns 10.

2. Step 2: Understand effect of missing await

   Without await, the delay is ignored in terms of method flow, causing unexpected behavior.

3. Final Answer:

   Missing await before Task.Delay, so delay is ignored. -> Option D

4. Quick Check:

   Always await async calls to run properly [OK]

Hint: Always await async calls like Task.Delay [OK]

Common Mistakes:

• Forgetting await before async calls
• Changing return type unnecessarily
• Thinking Task.Delay is invalid in async

5. You want to run two independent async tasks TaskA() and TaskB() concurrently and wait for both to finish before continuing. Which code snippet correctly achieves this?

hard

A. await Task.WhenAll(TaskA(), TaskB());

B. await TaskA(); await TaskB();

C. TaskA().Wait(); TaskB().Wait();

D. Task.Run(() => TaskA()); Task.Run(() => TaskB());

Solution

1. Step 1: Understand concurrency with async tasks

   Running await TaskA(); await TaskB(); runs tasks sequentially, not concurrently.

2. Step 2: Use Task.WhenAll for parallel execution

   await Task.WhenAll(TaskA(), TaskB()); starts both tasks concurrently and awaits their completion together.

3. Step 3: Evaluate other options

   TaskA().Wait(); TaskB().Wait(); blocks threads synchronously, and D starts tasks but does not await completion.

4. Final Answer:

   await Task.WhenAll(TaskA(), TaskB()); -> Option A

5. Quick Check:

   Use Task.WhenAll to await multiple tasks concurrently [OK]

Hint: Use Task.WhenAll to await multiple tasks together [OK]

Common Mistakes:

• Awaiting tasks one after another (sequential)
• Blocking with Wait() causing deadlocks
• Starting tasks without awaiting completion