Rajkumar Rangaraj

> The issue is related to all async method. > > Exceptions occurs in managed log file: > > ``` > [2022-08-05T08:48:29.6013132Z] [Error] Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe,...

Issue happens with .NET Core 3.1 and we see `FileLoadException` for `System.Runtime.CompilerServices.Unsafe.dll`. My previous note had an incorrect info modified to reflect the actual summary.

Found the root cause for an issue. Attached the deps.json generated from `TestApplication.StackExchangeRedis`. Deps.json shows that application has an indirect reference to `System.Runtime.CompilerServices.Unsafe.dll` ``` "Pipelines.Sockets.Unofficial/2.1.16": { "dependencies": { "System.Buffers": "4.5.1",...

@Kielek, I agree with you, we should postpone the fix for the issue. The issue happens only with .NET Core 3.1 which will eventually goes out of support by the...

If application has higher version of OpenTelemetry SDK than the Auto-Instrumentation OpenTelemetry SDK. Higher version wins and if there are breaking changes between these versions, auto-instrumentation might affect an application....

We might need to prioritize this issue. In the cases where `FileLoadException` are thrown like #1027 we could ask to refer the auto-instrumentation Nuget instead of those specific Nuget that...

> Unite Managed.Loader and StartupHook. Their logic is like 99% similar, I guess even static entrypoints could be the same. ** This would reduce some assembly loading and reflection (win:...

@dependabot rebase

@nrcventura Yes, we could close this PR. It's recommended to maintain the latest version of the packages in `OpenTelemetry.AutoInstrumentation.AdditionalDeps` to avoid dependency resolution issues.

To keep it clean, we could close this dependabot PR and create a new PR with all changes.