2. Real-world story

At Hospital patient record API, engineers use Custom Exceptions to return friendly error messages when transfers, logins, or file reads fail. This code shows the same pattern you will see in code reviews — simplified for learning, but structurally similar to production services deployed to Azure or on-prem IIS/Kestrel.

3. Problem without this concept

If you ignore Custom Exceptions, this is what teams struggle with:

• App crashes on network blip → angry users
• Empty catch blocks → silent data loss

4. Definition

Custom Exceptions is a core part of C# and .NET development. In plain terms: it helps you return friendly error messages when transfers, logins, or file reads fail.

5. Why do we need it?

You will see Custom Exceptions in console apps, Web APIs, background workers, and unit tests. Skipping it makes later modules (OOP, async, collections) much harder. Whenever I/O, network, or user input can fail — which is almost always.

6. Where is it used?

• ASP.NET Core middleware
• Payment gateway integrations
• File import jobs
• Return HTTP 400 for validation errors and 503 with retry for transient DB failures.
• Never swallow exceptions silently — log and return a safe message to users.

7. How it works

• Read the example top to bottom.
• Each line connects to Custom Exceptions.
• Run it with dotnet run, then change one value and predict the output before you save.

8. Syntax

Core syntax pattern for Custom Exceptions:

try
{
    // risky work
}
catch (SpecificException ex)
{
    // handle
}
finally
{
    // cleanup
}

9. Beginner example

Copy into a console project (dotnet new console → dotnet run).

try
{
    var json = File.ReadAllText("config.json");
    Console.WriteLine("Config loaded");
}
catch (FileNotFoundException ex)
{
    Console.WriteLine($"Missing file: {ex.FileName}");
}
catch (IOException ex)
{
    Console.WriteLine($"IO error: {ex.Message}");
}
finally
{
    Console.WriteLine("Cleanup always runs");
}

Line-by-line

10. Real project example

At Hospital patient record API, engineers use Custom Exceptions to return friendly error messages when transfers, logins, or file reads fail. This code shows the same pattern you will see in code reviews — simplified for learning, but structurally similar to production services deployed to Azure or on-prem IIS/Kestrel.

Production-style C#

// Hospital patient record API — global error handling pattern
public class OrderService
{
    public OrderResult PlaceOrder(OrderRequest req)
    {
        try
        {
            Validate(req);
            var id = SaveToDatabase(req);
            return OrderResult.Ok(id);
        }
        catch (ValidationException ex)
        {
            return OrderResult.Fail(ex.Message, retryable: false);
        }
        catch (TimeoutException)
        {
            return OrderResult.Fail("Payment gateway timeout", retryable: true);
        }
    }
}

Why teams use this: Teams that master Custom Exceptions ship fewer production incidents and pass code review faster on Hospital-scale systems.

11. Visual understanding

Input (user, file, API)
        │
        ▼
   Custom Exceptions logic in C#
        │
        ▼
   Output (console, HTTP response, file)

12. Internal working

• Roslyn compiler checks syntax and types before your program runs.
• CLR executes IL and provides services (GC, exceptions, threading).
• For this lesson, focus on behavior first — runtime details matter more as apps grow.

13. Advantages

• Readable code that new team members can follow
• Compiler catches many mistakes before deploy
• Huge .NET job market in India and worldwide

14. Disadvantages

• Takes time to learn if you skip fundamentals
• Overusing advanced features too early adds complexity

15. Best practices

• Catch specific exceptions, not bare `Exception` unless rethrowing
• Log with correlation id; return safe messages to users
• Use `throw;` to preserve stack trace

16. Common mistakes

• Copy-pasting without typing — your fingers need to remember Custom Exceptions syntax.
• Skipping error messages when the compiler fails — the red text usually tells you exactly what to fix.

17. Interview questions

Do this on your computer

1. Open Visual Studio or run dotnet new console -n LearnCustomExcept.
2. Paste the lesson example into Program.cs (or a new file).
3. Run the program and confirm the output matches your expectation.
4. Read the real-world section and name which part of a banking or e-commerce API would use this topic.
5. Change one line (amount, loop bound, or method name) and run again.
6. Read the real-world section and identify which layer (API, service, domain) uses this topic.
7. Run dotnet build and dotnet run locally — confirm output.
8. Change one value and predict the result before saving.

Experiments — try changing this

• Change a number or string in the example and run again — predict output first.
• Introduce a deliberate error (remove a semicolon) and read the compiler message.

18. Summary

• Custom Exceptions is used to return friendly error messages when transfers, logins, or file reads fail.
• Practice by editing the example yourself.
• Move to the next lesson when you can explain this topic in your own words.