Exception is thrown on non-standard IOC container due to use of Concrete classes. about opentelemetry-dotnet HOT 4 OPEN

Hey @PeterOscarsson any chance you could give me a small repro app using Unity + 1.8 OtlpExporter I can use to debug?

from opentelemetry-dotnet.

Sure, put the attached project in the OpenTelemetry catalog and put a breakpoint on
EnsureNoUseOtlpExporterRegistrations in
opentelemetry-dotnet\src\OpenTelemetry.Exporter.OpenTelemetryProtocol\Builder\OpenTelemetryBuilderServiceProviderExtensions.cs

Check with and without "UseUnityServiceProvider" in main Program.

OTelTest.zip

from opentelemetry-dotnet.

Thank you @PeterOscarsson! I opened this issue over in Unity: unitycontainer/microsoft-dependency-injection#96

I'm not opposed to just switching to an interface but I figured it would be good to gather their thoughts on the differing behavior before we took action. Seems like a behavior they might want to fix to prevent other things from breaking when choosing to use Unity over the M.S.E.DI container 🤷

from opentelemetry-dotnet.

@CodeBlanch ,Thats great, but I doubt you'll get an answer. Seems like its no longer activly maintained. Else I would have taken this up with them.
We are investigating switching DI but we have a huge CodeBase that depends on UnityContainer and it will take a while to do that.

from opentelemetry-dotnet.