You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure.Storage.Blobs12.17.0 and lowers together with dependencies is compiled against System.Diagnostics.DiagnosticSource4.6.0.
It was changed in 12.18.0 by Azure/azure-sdk-for-net#37418 and bumped to 6.0.1.
Lets consider TestApplication.Azure for 2.17.0 executed on .NET Fx 4.6.2
In runtime it will load System.Diagnostics.DiagnosticSource8.0.0 from local application folder.
If we fully remove reference to System.Diagnostics.DiagnosticSource it will work similar to v1.1.0 release. In runtime it will load System.Diagnostics.DiagnosticSource8.0.0 from tracer-home folder and 4.x from local application folder.
2 versions of the System.Diagnostics.DiagnosticSource are loaded to the same, main, app domain. It leads to the scenario where spans/activities are not registered by OpenTelemetry SDK.
'Azure.Storage.Blobs' 12.18.0+ with dependencies is compiled againsts System.Diagnostics.DiagnosticSource6.0.1. Redirections seems to be working fine for this version. All expected spans are recorder.
Proposal:
Release with fixes from 6a43c05 (test) and e1bafca (documentation)
Based on the findings solves the issue with riderecting old System.Diagnostics.DiagnosticSource4.x to the modern one.
The text was updated successfully, but these errors were encountered:
Kielek
changed the title
Azure.Storage.Blobs12.17.0 and lowers together with dependencies is compiled against System.Diagnostics.DiagnosticSource4.6.0.
[.NET Fx] Fix redirections for System.Diagnostics.DiagnosticSource 4.x
Nov 21, 2023
Azure.Storage.Blobs
12.17.0
and lowers together with dependencies is compiled againstSystem.Diagnostics.DiagnosticSource
4.6.0
.It was changed in
12.18.0
by Azure/azure-sdk-for-net#37418 and bumped to 6.0.1.Lets consider TestApplication.Azure for 2.17.0 executed on .NET Fx 4.6.2
for our release v1.1.0 without changes
In runtime it will load only
System.Diagnostics.DiagnosticSource
7.0.2
from local application folder.For our release v1.1.0 with removed reference to
System.Diagnostics.DiagnosticSource
In runtime it will load
System.Diagnostics.DiagnosticSource
7.0.2
from tracer-home folder and 4.x from local application folder.Lets consider code from this branch, commit: 3d36fed (before Azure test fix)
In runtime it will load
System.Diagnostics.DiagnosticSource
8.0.0
from tracer-home folder and 7.0.2 from local application folder.Test azure commit fix: 6a43c05
In runtime it will load
System.Diagnostics.DiagnosticSource
8.0.0
from local application folder.If we fully remove reference to
System.Diagnostics.DiagnosticSource
it will work similar to v1.1.0 release. In runtime it will loadSystem.Diagnostics.DiagnosticSource
8.0.0
from tracer-home folder and 4.x from local application folder.2 versions of the
System.Diagnostics.DiagnosticSource
are loaded to the same, main, app domain. It leads to the scenario where spans/activities are not registered by OpenTelemetry SDK.'Azure.Storage.Blobs'
12.18.0+
with dependencies is compiled againstsSystem.Diagnostics.DiagnosticSource
6.0.1
. Redirections seems to be working fine for this version. All expected spans are recorder.Proposal:
System.Diagnostics.DiagnosticSource
4.x
to the modern one.The text was updated successfully, but these errors were encountered: