Allow error mail report to be sent programmatically

[GoogleCodeExporter]

When the following code is executed:
Error error = new Error(ex, HttpContext.Current);
GotDotNet.Elmah.ErrorLog.Default.Log(error);

Include an option to perform the "errorMail" action either automatically
when .Log() is called or by specifying that an email should be sent in the
parameters.

See the discussion at:
http://groups.google.com/group/elmah/browse_thread/thread/b17cb4b5308b8013

Original issue reported on code.google.com by dgarcia...@gmail.com on 2 Aug 2007 at 10:33

[GoogleCodeExporter]

Fixed subject and turned this into an enhancement.

Original comment by azizatif on 2 Aug 2007 at 10:49

• Changed title: Allow error mail report to be sent programmatically
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by azizatif on 30 Oct 2007 at 9:22

• Changed state: Accepted
• Added labels: Component-Logic

[GoogleCodeExporter]

This is now possible via the new ErrorSignal class. See:
http://elmah.googlecode.com/svn/trunk/src/Elmah/ErrorSignal.cs

Calling ErrorSignal.Raise will go through the same set of events as when an 
unhandled exception is encountered. In effect, you'll get logging plus mailing 
(even 
filtering) if that's what's configured. As a result, this issue is being 
considered 
fixed for now. If there are issues with ErrorSignal, these should be reported 
as new 
issues.

Original comment by azizatif on 30 Oct 2007 at 9:26

• Changed state: Fixed

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by azizatif on 13 Sep 2012 at 3:51

• Changed state: New

[GoogleCodeExporter]

Hmm... Only problem with using ErrorSignal.Raise is it expects an exception, 
whereas ErrorLog.Log excepts a type of Elmah.Error.  If you wanted to create an 
elmah entry using an Elmah.Error type how would you do this (and send email) 
without throwing an exception?  Or can an exception be easily created using all 
elmah.error properties?

Original comment by Krit...@gmail.com on 21 Jan 2015 at 4:51