Timeline for Throw Custom Exception
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2019 at 19:39 | comment | added | John Wu | How is the client software to be deployed and supported, and by whom? If there is a network problem, do you expect that person to be able to troubleshoot it? If so, it would make things difficult if you hid the original exception from them. You should at least provide it as an inner exception. | |
| Oct 8, 2019 at 12:46 | answer | added | Phill W. | timeline score: 0 | |
| Oct 8, 2019 at 10:45 | answer | added | David Arno | timeline score: 2 | |
| Oct 8, 2019 at 5:40 | comment | added | Doc Brown | @DavidArno: your comment sounds good enough for an answer. | |
| Oct 7, 2019 at 18:55 | review | Close votes | |||
| Oct 12, 2019 at 3:05 | |||||
| Oct 7, 2019 at 14:47 | comment | added | Robert Harvey | Whether it's a "good" approach depends on whether or not it meets your specific needs. Does it? | |
| Oct 7, 2019 at 12:09 | comment | added | David Arno |
It looks good to me. Two things though: 1. it would be good to add the original HttpRequestException (or whatever exception it might be) to the InnerException of your IdentProviderNotAvailable. and secondly, it's convention to put Exception on the end of the name of all exceptions. Whether that's a good convention or not is another issue entirely ;)
|
|
| Oct 7, 2019 at 11:35 | review | First posts | |||
| Oct 10, 2019 at 6:57 | |||||
| Oct 7, 2019 at 11:33 | history | asked | devsmn | CC BY-SA 4.0 |