We have this functionality in a non-flexible way already in opentracing-contrib/csharp-netcore which I would create a PR for to unify the usage. The idea is, to have Microsoft.Extensions.Logging support for any .NET Core framework, without having to use the full opentracing-contrib/csharp-netcore or even dependency injection. So splitting it would be the best way in my opinion.
I'm one of the maintainers of jaegertracing/jaeger-client-csharp and opentracing-contrib/csharp-grpc. I would like to add the code base using
Microsoft.Extensions.Logging
to theopentracing-contrib
project.We have this functionality in a non-flexible way already in opentracing-contrib/csharp-netcore which I would create a PR for to unify the usage. The idea is, to have
Microsoft.Extensions.Logging
support for any .NET Core framework, without having to use the full opentracing-contrib/csharp-netcore or even dependency injection. So splitting it would be the best way in my opinion./CC @yurishkuro