Investigate Ways to Reduce Dependence on Reflection for EventSource #22793
Labels
area-System.Diagnostics.Tracing
enhancement
Product code improvement that does NOT require public API changes/additions
Milestone
EventSources currently require reflection for both manifest-based logging and tracelogging. The latter is required, because there is no concept of subclasses or event methods - just calls to Write public methods on EventSources.
However, we can do better with manifest-based logging. There is currently an IL transform in the toolchain that triggers for a well-known set of EventSources in the framework and pre-generates metadata for them so that reflection is not used at runtime. We should consider expanding this transform for two cases:
The text was updated successfully, but these errors were encountered: