Lurgle.Logging v1.1.14 and Lurgle.Alerting v1.1.9 Released
I've pushed out updates to Lurgle.Logging and Lurgle.Alerting today.
The Lurgle.Logging update is minor - I noticed that Log.Add wasn't correctly passing the calling method, source file, and line number.
Lurgle.Alerting has received a more substantial update:
Alerting.IsDebugis a global boolean variable that is set via
Alerting.SetDebug(). When set, it will ensure that recipients are automatically replaced with the debug email address. If you have a "debug mode" that can be switched on or off for your app, just make sure you set
Alerting.IsDebug(true)for debug mode, configure
MailDebug, and let Lurgle make sure you don't accidentally leak data while testing!
MailDebugis a new setting for the debug email address. This affords opportunity to differentiate a debug email address from your default
- Comma- (or semi-colon) delimited email address strings will now always be consistently handled. If a delimited email address string is passed to one of the
Bcc()methods, it will automatically be parsed into the list of recipients.
ReplyTo()also handle comma-delimited strings, but since these can only contain one email address - the first valid email address will be selected.
- Invalid email addresses will automatically be filtered out
Alerting.Init()method will automatically validate that the
MailSubjectconfig values have been configured.
Alerting.Init()failures are reported via the
Alerting.AlertFailuresstatic list, for handling via your code.
This helps to make Lurgle.Alerting even more useful and reliable!
You can get the updated Lurgles via the following fancy links: