Debugging is one of our most important experiences, and there are instances where it's not working for some subset of users in a way that we can't quite reproduce.
Adding telemetry will enable us to understand how widespread problems may be and how well each of our fixes are addressing the issue so we can be more confident in the quality of the product we put out.
We can detect this by checking whether debugging was started, and hit a certain point during attach-to-process. And actually... better yet... if we have a good way of detecting the issue, we can offer the user steps to get past it (maybe print a message in the debug output window directing them to github).
Debugging is one of our most important experiences, and there are instances where it's not working for some subset of users in a way that we can't quite reproduce.
Adding telemetry will enable us to understand how widespread problems may be and how well each of our fixes are addressing the issue so we can be more confident in the quality of the product we put out.
We can detect this by checking whether debugging was started, and hit a certain point during attach-to-process. And actually... better yet... if we have a good way of detecting the issue, we can offer the user steps to get past it (maybe print a message in the debug output window directing them to github).