On Sun, 22 Mar 2020 at 04:45, Brown, Michael <m...@purdue.edu> wrote:
> Are there better replacements for Log4net? What would it take to migrate > to them? It depends how far log4net is integrated into a codebase. There are good interfaces available [1] to write code against. Dependency injection frameworks have also become very popular [2]. If code is written against these or any other generic interfaces, the underlying logging framework implementation can be replaced easily. Of course there are also issues relating to logging framework configuration files and others if parts of the logging framework (i.e. log events via remote appender) have been integrated into monitoring or application logic. This can be a challenging task if the interfaces between the various parts of an application are unclear. This situation may be a good moment to improve an existing codebase. Or it could be a good reason to become the maintainer of log4net. The PMC does support if at least three individuals step forward now. Please note that the codebase of log4net does not disappear. It is still there, hopefully for the public good. [1] https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger?view=dotnet-plat-ext-3.1 [2] https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection?view=dotnet-plat-ext-3.1 -- Dominik Psenner
