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
Right now, all tracelogging (aka self-describing) events can't really have strong typing information. This makes usage of them very hard. I would love to have a way to create strongly typed version of them, similar to what is supported for Manifest events.
The text was updated successfully, but these errors were encountered:
I have not experimented with this, but it does seem do-able. TraceLogging support is somewhat bolted on in TraceEvent and is mostly handled by DynamicTraceEventParser. I suspect it would be possible to implement such a thing by creating a new TraceLoggingTraceEventParser similar to DynamicTraceEventParser that can return a strongly-typed payload from an event-specific property. Instead of keeping track of the event in the main lookup logic of TraceEvent as is done for manifested events, it would register itself as a dynamic parser, and would keep its own internal lookup table of event --> strongly typed template.
There has not been significant interest in this area which is why nothing has been done here. I would certainly support such a change if you were interested in contributing it.
Right now, all tracelogging (aka self-describing) events can't really have strong typing information. This makes usage of them very hard. I would love to have a way to create strongly typed version of them, similar to what is supported for Manifest events.
The text was updated successfully, but these errors were encountered: