C# Developer Shares Key Lessons on Handling Exceptions the Right Way

A C# developer writing for DEV Community outlined lessons learned about proper exception handling while building .NET APIs. The author found that catching exceptions without acting on them — known as silent catching — masks bugs and complicates debugging in production environments. A key takeaway was to catch only specific exceptions, such as FormatException or ArgumentNullException, when there is a clear, meaningful response to the error. The article also covered throwing custom exceptions to represent business-level problems, like a UserNotFoundException, making errors more informative. Finally, the author recommended using global exception-handling middleware in ASP.NET Core to centralize error management rather than repeating try-catch blocks across every controller.