Open GoogleCodeExporter opened 9 years ago
Original comment by azizatif
on 19 Oct 2010 at 12:26
Similar to the Exception Data dictionary, I think this would be an excellent
addition.
Original comment by marc.c.l...@gmail.com
on 28 Oct 2010 at 6:21
I hope we'll see this implemented soon.
See also http://code.google.com/p/elmah/issues/detail?id=162
Original comment by fabrice....@gmail.com
on 12 May 2011 at 2:58
See also comment #12[1] in issue #162.
[1] http://code.google.com/p/elmah/issues/detail?id=162#c12
Original comment by azizatif
on 12 May 2011 at 9:05
[deleted comment]
[deleted comment]
Had a similar thought - but turned out we had a custom exception that wasnt
calling base with the passed in exception.
As long as we do that, we got the details of the inner exception as this is
included in the toString of Exception
For extending though - be nice if elmah exposed out assinging a Func to methods
for getMessage and getDetails in error.cs - so something like:
Elmah.Error.GetMessage = (e) => e.Message + getExtraExceptionInfo(e);
That way anyone could extend and augment what got logged
Original comment by stevebak...@gmail.com
on 9 Feb 2012 at 1:46
hi,
Any idea what version this enhancement will be added?
Original comment by andycw...@googlemail.com
on 25 Mar 2012 at 3:04
Bump, this would be useful.
Original comment by byte...@gmail.com
on 15 May 2012 at 1:26
really would like to see this too
Original comment by paul.car...@gmail.com
on 9 May 2013 at 2:29
This would be a great addition. I might see if I can't get it into a custom
build for myself, if I do I'll provide a patch.
Original comment by kyleh...@gmail.com
on 4 Oct 2013 at 12:52
[deleted comment]
This issue has been migrated to:
https://github.com/elmah/Elmah/issues/178
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of
any further development.
Original comment by azizatif
on 25 Aug 2015 at 8:19
Original issue reported on code.google.com by
ad...@sf4answers.com
on 5 Jul 2010 at 3:32