Exception when logging exception: is it correct to ignore them?
My question is specific to php, but i think it can be useful in other languages.
Exception when logging exception: is it correct to ignore them?
My question is specific to php, but i think it can be useful in other languages.
DAL Exception handling in a MVP application
In a MVP win forms application I’m handling exceptions as follows in DAL.
DAL Exception handling in a MVP application
In a MVP win forms application I’m handling exceptions as follows in DAL.
DAL Exception handling in a MVP application
In a MVP win forms application I’m handling exceptions as follows in DAL.
Multiple handlers of an exception, and handling exceptions in the UI
Related to: Is onError handler better than exceptions?
How much data should exceptions hold?
Almost all the exceptions I have ever written have been very lightweight, containing a String message and optionally a throwable. In some situations I have included some application specific enum or some other field.
How much data should exceptions hold?
Almost all the exceptions I have ever written have been very lightweight, containing a String message and optionally a throwable. In some situations I have included some application specific enum or some other field.
Java-Like ‘throws’-information in method signature C#
From Java I know that the signatures of methods that can throw exceptions contain a throws block, that contains the Exception(s) that might be thrown.
In C# there is no such thing and it is also not common practice to include such info in the XML-Header.
Is there a generally accepted way of drawing attention to potential exceptions or a place to commonly denote them?
How to ensure the success of processes after a deadlock exception occurs?
No matter the programming language is and whatever the database is, the concept should be the same: