Log4Net does not get that much attention any more. From my understanding it served as an alternative for Log4J, but today better and more modern solutions have been created. I migrated a codebase over to .NET Core a couple of years ago, and it seemed that Log4net had issues running on Linux because of kernel calls inside their codebase. If you look at the version history on NuGet, it had just 3 patch releases last... Source: over 1 year ago

I'm going to look at psframework mentioned elsewhere, but I make use of .NET NLog https://nlog-project.org/. it's not terribly hard to wire up, and is pretty feature rich. Source: over 1 year ago

On the other hand, NLog is a flexible and free logging platform for various .NET platforms, including .NET standard. NLog makes it easy to write to several targets. (database, file, console) and change the logging configuration on-the-fly. - Source: dev.to / almost 3 years ago

For instance, we use NLog for our .NET projects. The nice thing there is that you use an external configuration file (nlog.config or your application's default configuration file) to configure logging. You can specify various "loggers" and "appenders", so that you can route your logs to several places, and all you have to do is change configuration between environments. You can do things like allowing for... Source: about 3 years ago

I was given discarded Lenovo T470s laptops that were put in the assembly department so the personnel could use the application. Because I was tied to Windows and had to create a GUI for easy usage, I decided to create a C# program in Microsoft Visual Studio because creating a GUI for Windows was very easy that way. It would create local HTML files using the Barcode Rendering Framework NuGet package for creating... - Source: dev.to / about 3 years ago

Check out our README for the latest status. - Source: dev.to / over 2 years ago

If you haven't heard of DevStream yet, please have a quick glance over our README. - Source: dev.to / over 2 years ago