You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using MVCMailer which depends on an HttpContext to send out mail.
In some cases I'm sending mail from a WebJob, or in an async task that is used in a flow that calls ConfigureAwait(false) so I lose the context before I hit the MVCMailer code.
My options seem to be:
Never use ConfigureAwait(false) (so many of my services use Mailing at some point, so one instance of this will remove the context I need)
New up an HttpContext if needed so that I can mail despite not having one
Not use MvcMailer and use a third party
I'm looking for the fast and easy solution - newing up an HttpContext if needed. Is this possible?
The text was updated successfully, but these errors were encountered:
Question here: http://stackoverflow.com/questions/40365517/create-new-httpcontext-for-mvcmailer-so-i-can-use-async-await
I'm using MVCMailer which depends on an HttpContext to send out mail.
In some cases I'm sending mail from a WebJob, or in an async task that is used in a flow that calls ConfigureAwait(false) so I lose the context before I hit the MVCMailer code.
My options seem to be:
Never use ConfigureAwait(false) (so many of my services use Mailing at some point, so one instance of this will remove the context I need)
New up an HttpContext if needed so that I can mail despite not having one
Not use MvcMailer and use a third party
I'm looking for the fast and easy solution - newing up an HttpContext if needed. Is this possible?
The text was updated successfully, but these errors were encountered: