I suggest you ...

Logging to Enterprise Library Semantic Logging

Add Enterprise Library Semantic Logging Application Block as a backend to PostSharp Diagnostics

36 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Gael FraiteurGael Fraiteur shared this idea  ·   ·  Admin →

    7 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Mike-EEEMike-EEE commented  · 

        Forget EntLib. It's done for. Check out Serilog with the Sinks FTW: https://github.com/serilog/serilog/wiki/Provided-Sinks

        It looks like if you support Serilog, you support everything (but it would be nice to have a provider-model regardless).

        Also, if anyone is interested, you can actually get Serilog working with PostSharp for now by making use of the System.Diagnostics.Trace logging back-end option, and making use of the trace listener created for it here: https://github.com/serilog-trace-listener/SerilogTraceListener

      • Mike-EEEMike-EEE commented  · 

        It's too bad they don't show the dates of when comments are posted, because I have changed my tune considerably around this, primarily because of the fact of ETW is not cross-platform and is Windows-only. Additionally, after working a lot with it, it is a rather terrible API to work with, despite its improvements in the .NET adaptation.

        Furthermore, the P&P group has gone south and there is hardly any activity there anymore. In fact, the two primary/popular projects that are used anymore -- Unity and Prism -- have been jettisoned and outsourced to external parties.

        Nonetheless, it might be interesting to still have this available along w/ a cross-platform solution such as Xamarin insights. Also, I am not sure, but Application Insights might work, too?

      • Mike-EEEMike-EEE commented  · 

        One thing that the solution I provide below doesn't do is auto-generate the EventSource. This is something that ESProxy does, and PostSharp's implementation should do as well. That is, given an arbitrary interface, PostSharp should auto-generate an EventSource from it.

        More here:
        https://github.com/jonwagner/EventSourceProxy

      • Mike-EEEMike-EEE commented  · 

        This would be amazing. Please add!!! ETW is a pretty big deal and the way that P&P group is now suggesting to log. It is also misleading that your site says that it supports "Enterprise Library" logging and you do not support this.

      Feedback and Knowledge Base