I suggest you ...

Get rid of the Logging and ExceptionHandling Application Blocks

For a long time I have felt that the Entlib logging and other logging frameworks like Log4Net, have been going in the wrong direction and worse have allowed the actual MS Framework guys to rest on their laurels. We should not need to log exceptions, the .NET framework should automatically do it for us. We should not have to add tracing statements to capture method calls and parameters being passed in, the Framework should do it for us.
Then a couple of years ago we started using AviCode, and it turns out that this is true, Avicode is able to detect exceptions, and you can see full traces etc. So why do we still want to log things. Since avicode has been bought out by MS and the product is now built into SCOM We need guidance on how to use the tooling that is built in.

16 votes
Vote
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)
    You have left! (?) (thinking…)
    NoelNoel shared this idea  ·   ·  Admin →

    1 comment

    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...
      • Dzmitry LahodaDzmitry Lahoda commented  · 

        Cool. Can I use AviCode for my Excel VSTO addin instead of EntLib?

      Feedback and Knowledge Base