Labs > Visual Studio Extension: Debug Single Thread
This Visual Studio extension adds two shortcuts and toolbar buttons to allow developers to easily focus on single threads while debugging multi-threaded applications.
It dramatically reduces the need to manually go into the Threads window to freeze/thaw all threads but the one that needs to be followed, and therefore helps improve productivity.
Features:
- Restrict further execution to the current thread only. Will freeze all other threads. Shortcut: CTRL+T+T or Snowflake button.
- Switch to the next single thread (based on ID). Will change current thread and freeze all other threads. Shortcut: CTRL+T+J or Next button.
Feature requests are welcome here. Official repository here.
You can download the VSIX package directly from the Visual Studio Gallery.
I have added this extension to Visual Studio 2010, it success. However, it’s inactive??!! What I have to do to activate it??
Hi Aqeel, you just need to restart Visual Studio for the extension to be activated.
Many thanks, install this on VS 2017 RC
This extension is a piece of GOLD. Thanks Erwin !!!
Hi) Installed your extension on VS2022 Community, restarted VS, but there’s no snowflake button and shortcuts aren’t attached to any command. Reinstalled, restarted – no effect. Is Debug Single Thread still supposed to be working, please? ) Thanks!
@Jim, Yes, it is still working fine. When not debugging, the button will show up greyed out instead of in blue, so it can be easily missed (there is nothing to click anyway at that point). If you have an issue, it is best to ask on GitHub.
@Erwin, Hi) thank you. Where exactly should I look for a snowflake button? I’m assuming Threads window, where there’s normally only a green « play » button? Cause there’s no snowflakes there or anywhere near (. I looked for a screenshot of a VS to see where it is, I might be missing it somehow. But again, commands don’t work either. Will ask on a GitHub, thank you!
@Jim, see on this screenshot: https://imgur.com/a/RsHh78v. Let’s continue the conversation on GitHub if needed. Cheers.