Support middleware (or Elm option) to log errors to the Windows Event Log

[JesperTreetop]

ASP.NET 4 and older logs escaped exceptions to the Windows Event Log with the event ID 1309. This seems like a good middleware to have in Diagnostics to also make it hosting-independent (although maybe not platform-independent; Mono seems to do wildly different things depending on configuration). Unsure if this is best implemented as a standalone middleware or as an option to the Elm infrastructure (maybe because Elm isn't really detailed anywhere; it seems like an exception VCR and the name hints at ELMAH).

[davidfowl]

This wouldn't be middleware, it would be a logger provider. The middleware just calls into whatever log providers are registered.

[JesperTreetop]

I didn't notice that the logging interfaces took Exception objects. That makes sense, as long as the hosting environment catches and logs these exceptions (or otherwise there would need to be middleware at least to do that).

[JesperTreetop]

And that middleware was this middleware, ErrorHandlerMiddleware, of course.

Is an event log logger provider planned or are you accepting pull requests for this?

[Eilon]

@JesperTreetop I'm closing this issue because it isn't a Diagnostics issue. Can you re-start the discussion in the https://github.com/aspnet/Logging/ repo?