What new or enhanced feature are you proposing?
Add a NameValueCollection as an optional overload to the Elmah.Error class.
(and have appropriate renders in the E-mail/Web viewer)
What goal would this enhancement help you achieve?
I currently have an application which does its own error logging into the
Windows Event Viewer. It isn't especially good and I have some hooks to change
it. I recently made it so that it would use Elmah.Error to log errors and that
works quite well. However the whole application runs mostly in 1 "page"
(Default.aspx) but is made up of hundreds of pages and views. Which means
figuring out where the error actually came from in the ServerVariables is nigh
impossible. The error logging that I can hook into, however, has this
information. It'd be nice to be able to pass Elmah.Error a NameValueCollection
that can have whatever the developer sees as necessary to be seen in a log
beyond form/servervariables/querystring which are all non-editable.
Original issue reported on code.google.com by iamw...@gmail.com on 14 Feb 2012 at 9:28
Original issue reported on code.google.com by
iamw...@gmail.comon 14 Feb 2012 at 9:28