What is considered best practice associated with Exception Handling inside an ASP.NET HttpHandler? Should Exceptions not able to be handled be allowed to flow upwards through the chain as one would do in general or should all Exceptions be caught and “handled” in the handler and allow nothing past?
What is considered best practice associated with Exception Handling inside an ASP.NET HttpHandler? Should
Share
My suggestion will be simple: if you cannot “fix the problem” then don’t swallow the exception – let it propagate. Otherwise you’ll most likely face with unexpected behavior of your application.