-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Support for Extended Data #703
Support for Extended Data #703
Conversation
FIleVersion 17
Attached is binary log for testing if needed. |
this is nice! I think if extended data is available, we should manufacture a message as a child node of the extended event, and put the full text in there. Also if extended metadata is present, add metadata child nodes for each metadata |
See |
@@ -549,7 +550,7 @@ | |||
<Setter TargetName="messageText" Property="Opacity" Value="0.25" /> | |||
</DataTrigger> | |||
</DataTemplate.Triggers> |
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.
Probably need to change these to HierarchicalDataTemplate.Triggers
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.
Surprised that it works, but OK
Implementing: dotnet/msbuild#9091
Context
MSBuild introduced new concept of Event args Extended data which are supposed to address need to extend events.
One of its most appealing use cases is for passing extended compiler error and warning structured information into msbuild logging infrastructure. Having such info in binlog and viewer might be of use.
Changes Made