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
".NET itself - both the VS profiling tools (the database tool in this case) and dotnet-trace end up being unable to collect ActivityIds for the Stop events despite them being marked as Activity events in both scenarios, making us unable to correlate the query start and stop events together when opening these files in Visual Studio."
Hi @timmac-qmc, to clarify, are you emitting these Activity2Start/Stop events from your program? Do you happen to have a simple repro that demonstrates the ActivtyId missing from the Activity2Stop event when collecting a trace with dotnet-trace?
I'm not very familiar with the Activity events, do you know if the ActivityId is present in the Activity2Stop events when using .NET 8.0 or any prior version of .NET?
Description
Raising this issue as recommended here https://developercommunity.visualstudio.com/t/Database-Profiler-is-completely-broken-1/10771227#T-ND10813008
".NET itself - both the VS profiling tools (the database tool in this case) and dotnet-trace end up being unable to collect ActivityIds for the Stop events despite them being marked as Activity events in both scenarios, making us unable to correlate the query start and stop events together when opening these files in Visual Studio."
Configuration
Regression?
Unknown
Other information
Relevant information provided in the linked bug report: https://developercommunity.visualstudio.com/t/Database-Profiler-is-completely-broken-1/10771227#T-ND10813008
The text was updated successfully, but these errors were encountered: