-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic netfx assembly redirection #1825
Conversation
This reverts commit e291eb8. We need some extra work to automate this process and also a friendly way to register assemblies in the GAC.
5c2e20a
to
f6fb7c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Briefly checked. I will revisit it on Monday.
I left only some nit comments.
src/OpenTelemetry.AutoInstrumentation.Native/netfx_assembly_redirection.h
Outdated
Show resolved
Hide resolved
2nd round with changelog text
I'm having second thoughts about having a static list of versions: we could look at startup for the assemblies shipped with the app to update the version of the redirection. Anyway, I would prefer to address that in a separate PR. |
…-instrumentation into net-fx-auto-redirect
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, on comment to review.
I suppose that it will increase cold start time. Additional measurements are needed. |
…-instrumentation into net-fx-auto-redirect
Why
To automate instrumentation of .NET Framework without requiring binding redirection and reducing the cases that adding dependencies to the projects are needed.
Fixes #1646
What
netfx
folder and use it to generate a map of redirections to be used by the native profiler in_WIN32
compilation.netfx
.The risk is that dependencies are changed at runtime and it is possible that issues only show up when certain code paths are executed. A much safer path would be to have the application reference a NuGet package with all the dependencies required by automatic instrumentation.
To minimize the risk of downgrading packages used by the application, details here, we need the work from #1824 and #1823.
Tests
Checklist
CHANGELOG.md
is updated.