muhaook

Hi @Kielek , during my prototype, I noticed System.Data got loaded in shared appdomain on .NET framework. ``` [2022-08-21T15:54:07.404708400Z] [33532|35180] [debug] Comparing signature for method: System.Data.Common.DbCommand..ctor [2022-08-21T15:54:07.404737400Z] [33532|35180] [debug] Enqueue...

@pjanotti , as far as I know, below means it is a shared appdomain ``` [2022-08-21T15:54:07.404761800Z] [33532|35180] [debug] ModuleLoadFinished stored metadata for 140712098334424 System.Data AppDomain 140713692092832 EE Shared Assembly Repository...

Hi @Kielek and team, is this feature still on schedule? It would be very useful if we can add custom bytecode instrumentations from plugins.

Thanks @pjanotti , we have a few requirements that depend on the feature of the custom bytecode instruementation, e.g. - use bytecode instrumentation to inject a middleware for ASP.NET Core...

Hi @zacharycmontoya , please let me know when the fix is available. I can verify it on my envs. Looks like the fix targets 1.2.0. Do you know the ETA...

My understanding is the root cause is both CoreCLR (for .NET core) and CLR (for .NET framework) were brought up in an application pool. Looked into the native code, I...

Hi team, I made a quick fix to honor the first profiler:  seems it fixed the bytecode instrumentation issue on my env (need thorough tests though) I wonder the...

Comments from @pjanotti : Notice that on Windows, tools like `PerfView `use ETW events not a CLR Profiler . The key question is if the application is .NET Framework or...

Sure @pjanotti , attached please find logs for win2012r2 and win2022: [logs_win2012r2.zip](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/files/11141672/logs_win2012r2.zip) [logs_win2022.zip](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/files/11141673/logs_win2022.zip)

@Kielek , i do not think this is a big issue. it is unlikely that PROD env has only 1 CPU. please feel free to postpone or close this issue.