--- title: "Best Practices for Exceptions in ASP.NET Core" url: https://daily.dev/posts/best-practices-for-exceptions-in-asp-net-core-eews3z8nt source_url: https://www.telerik.com/blogs/best-practices-exceptions-aspnet-core type: article source: "Telerik" published: 2026-06-29T13:21:29.786Z updated: 2026-07-03T02:17:44.728Z tags: ["c#", "aspnet"] reading_time: 8 upvotes: 20 comments: 2 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Best Practices for Exceptions in ASP.NET Core **[Telerik](https://daily.dev/sources/telerik)** · 8 min read · 20 upvotes · 2 comments ## Summary Covers best practices for exception handling in ASP.NET Core, emphasizing that exceptions should be reserved for truly unpredictable situations rather than expected errors like input validation. Introduces the Result Pattern as a structured alternative for predictable failures, returning a typed Result object with IsSuccess and Error properties instead of throwing exceptions. Also covers creating custom exceptions for better traceability and domain clarity, and helper methods to avoid duplicate exception throwing across a codebase. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@jonathanaugustodotore** · 0 upvotes > I usually implement a "MainResponse" DTO and put return properties to make custom returns. exceptions must be implemented for only NON EXPECTABLE errors. Or try to custom and create exception handlers for each domain or flow. **@luispsarmiento** · 0 upvotes > A little bit summary: the exception handlers is to unexpected failures and the result patter is to domain failures. --- Tags: [#c#](https://daily.dev/tags/c#), [#aspnet](https://daily.dev/tags/aspnet) [View this post on daily.dev](https://daily.dev/posts/best-practices-for-exceptions-in-asp-net-core-eews3z8nt)