Should we repurpose this library to make a bridge adapter for Microsoft.Extensions.Logging ?

[Aaronontheweb]

The Common.Logging library has been deprecated, somewhat, as its role in the .NET ecosystem was effectively usurped my the standard libraries Microsoft introduced as part of the .NET Core rollout in early 2017: Microsoft.Extensions.Logging

Should we repurpose this library to target those going forward? Or should we create an entirely new library for the purpose of targeting those? We can programmatically inject a configured ILogger from Microsoft.Extensions.Logging via the new Setup type introduced in Akka.NET v1.4.

Or, we can add a new library altogether as part of the Akka.NET core library (it'd be a separate package, but part of the main repository) - what should we do?

[ericsampson]

Microsoft.Extensions.Logging.Abstractions right?

[Aaronontheweb]

@ericsampson yep - whatever the best base library is to target the logging abstractions inside ASP.NET Core and so on

[Aaronontheweb]

My vision here: make it trivially easy for someone to take the logger they wired up for ASP.NET Core and inject it into an Akka.NET ActorSystem at startup.

[Danthar]

I would say re-purpose this library to be a bridge between Microsoft.Extensions.Logging and the Akka.Net logging infra.
And then, in time, deprecate the logging specific plugins.
The only thing we probably would need to pay some special attention to, i think, is how we are going to expose the logging format. Since some logging extensions have some fairly specific definitions, to utilize their own logging specific features to the fullest.
I'd expect we would lose some functionality there due to the abstraction that Microsoft.Extensions.Logging enforces. But haven't used it myself yet, so it might be a non-issue.

[Aaronontheweb]

@Danthar alright, I'll give this a stab inside the main repository and see if I can come up with a minimally invasive prototype.