Logging information in .NET, or really in any production application, is invaluable. In many cases, developers don’t have direct access to the production environment to debug issues. Good quality logs are the difference between solving problems like Sherlock Holmes and stumbling upon solutions like Inspector Jacques Clouseau. As you can imagine, we’re pretty big on logging here at Stackify, and we’ve written quite a few other blog posts on .NET logging frameworks. I’d encourage you to try out the search and read a few of our previous articles.
Top .NET Logging Frameworks Comparison
In this article, we’ll take a look at three of the most popular logging frameworks in the .NET space: log4net, NLog, and Serilog. If you’ve read any of my comparison articles in the past, you’ll know that I typically end up with some wishy-washy conclusion like, “It all depends on your situation” or some variation of “different spices for different mices.” But not this time! This time, I promise to declare one winner; one logging framework to rule them all and in the CLR bind them.
from DZone.com Feed https://ift.tt/2PPSTcu
No comments:
Post a Comment