-
Notifications
You must be signed in to change notification settings - Fork 292
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
Visual Studio Diagnostic Tools Events missing in Microsoft.Data.SqlClient #2634
Comments
This issue is a duplicate of issue #93. However, you may want to consider SqlClient's EventSource implementation. |
@arellegue I don't really think this is a duplicate. They are the same root cause but #93 never addressed the Visual Studio side of this issue. Only really App Insights. For a developer debugging in real-time the events showing up in the Diagnostic Tools was a huge time saver. I will look at Event Source. |
@Banner-Keith I have reached out to the Visual Studio team internally to get some guidance on this issue and its potential fix. I will update this thread when I have an answer for you. |
@JRahnama thank you for that. I really appreciate it. |
@Banner-Keith this issue is external to SqlClient. Can you open a ticket at Developer Community(visualstudio.com) and follow there? Seems like the action needs to be taken from their side to include M.D.SqlClient in their product. |
Closing the issue as it is external to SqlClient. Feel free to comment here or open a new issue. |
We recently switched from System.Data.SqlClient to Microsoft.Data.SqlClient. One difference we've noticed that's been quite painful is that we no longer get events logged in the Visual Studio Diagnostic Tools window showing ADO.net queries.
Example:
It doesn't appear that there's a way to get that experience out of the box. Is there some way we can at least dump this information in the debug log when we are debugging a running app?
I searched for related issues and found this in a different issue about tracing, but it wasn't addressed there since it was really a different issue. I thought it would be worth tracking down separately.
Originally posted by @jwooley in #93 (comment)
The text was updated successfully, but these errors were encountered: