Closed OlzhabaevSh closed 3 months ago
We found a comment to the documentation where they mentioned regarding this bug: https://github.com/dotnet/docs/pull/28826
Link for the issue: https://github.com/dotnet/runtime/issues/39353
For development purposes you can go to Services -> 'VSStandardCollectorService150' and disable it
The bug is fixed and will be available in VS 17.11. We will use that date as a release day for the extension
VS 17.11.x has been released and it fixed the bug!
we are good to go!
Describe the bug The Diol extension for Visual Studio doesn't show response's logs.
To Reproduce Steps to reproduce the behavior:
Play
/api/default-client/bing
Http
you will see the request but no response.Expected behavior If you check
Diagnostics
tab you will see that we recieve response's logs. But the problem is thekey
. The good news is the bug is not releated with our code. For some reasons Visual Studio brokesActivityIds
and you will not see the issue if you run the app withdotnet run
from ternminal.You can read more here
What we can do:
Screenshots Not need
Desktop (please complete the following information):
Smartphone (please complete the following information): Not need
Additional context Let me cope small workaround from documentation:
There is a known issue where Visual Studio debugger may cause invalid Activity IDs to be generated. Either don't run this sample under the debugger or set a breakpoint at the beginning of Main and evaluate the expression 'System.Threading.Tasks.TplEventSource.Log.TasksSetActivityIds = false' in the immediate window before continuing to work around the issue.