All 16 Exception Handling questions
More in Exception Handling
How do custom exception classes work in C#, and what's the recommended convention for creating one? What is exception filtering using the 'when' clause, and what advantage does it offer over catching and manually re-throwing? Why does 'throw;' (bare throw) preserve the original stack trace, while 'throw ex;' does not? When should you create custom exceptions vs use built-in ones? How does exception handling interact with async/await, and how are exceptions from an async Task propagated to the awaiting caller? How does AggregateException work with Task.WhenAll() when multiple concurrent tasks throw exceptions? What is 'exception filtering with side effects' and why is it considered a controversial but sometimes useful technique for logging? How would you design a robust global exception handling middleware in ASP.NET Core to convert unhandled exceptions into consistent API error responses? How does exception performance (throwing/catching) compare to normal control flow, and why should exceptions generally NOT be used for expected, routine control flow?
Advertisement
Back to results for “Exceptions”
C# › Exception Handling

What is the recommended strategy for exceptions in a layered/enterprise app?

Advanced

Answer

Throw specific exceptions in lower layers, don't swallow them, translate to a consistent response at the boundary (middleware/ProblemDetails), and log with context. Avoid using exceptions for control flow.
app.UseExceptionHandler();  // central translation to ProblemDetails
Real-world example One middleware converts domain and unexpected exceptions into consistent JSON errors for all API clients.
All 16 Exception Handling questions