ReAttach gives you an easy way to ReAttaching your prior debug targets. ReAttach stores your attach history for you and provides toolbar, menu and keyboard shortcuts for easy access.
ReAttach gives you an easy way of reattaching to your prior debug targets. This is especially useful when working with IIS-processes, test runners and web browsers. ReAttach stores your attach history for you and provides both toolbar and menu options for easy access.
The hotkey sequence CTRL+R, CTRL+A is used to ReAttach to your latest target (top of the history list). If your process is not currently running, ReAttach will ask you to start it and attach to it as soon as it becomes available.
What's new in 2.3?
Support for Visual Studio 2019. Unfortunately at the cost of several older versions (see old versions).
What's new in 2.0?
Build before ReAttaching: You can now enable auto rebuilding before reattaching to targets.
Multiple debug engines: Reattach will now remember specific (and multiple) debugging engines and attach to them accordingly.
Minor fixes: Various bugs and minor tweaks.
What's new in 1.1?
Better UI support: You now have dedicated buttons and a toolbar that you can use to customize your experience (they're placed under the debug category).
Multiple targets: Attached targets are temporarily hidden/disabled in the history. This allows you to ReAttach to multiple targets in a row using the top-level shortcut and hotkeys.
More hotkeys: In addition to the original one, CTRL+R, CTRL+[1-5] can also be used, allowing attaching to older targets.
Remote debugging support: Experimental for now. When you attach to a remote target the server required is also stored. When ReAttaching, a different transport qualifier is used.
Minor fixes: A few bugs, language changes, UAC support etc.
The ReAttach menu controller dropdown showing two targets in the users ReAttach history.
How does it work?
When debugging is started and the underlying reason is a user attach, ReAttach stores process path, username and PID in the registry (in a subkey called ReAttach located under the currently running visual studio user's key). Once a ReAttach is made the following steps occurs:
All candidates (running processes) with matching path and username are filtered out.
If there's a candidate with a matching PID that process is immediately selected and attached to.
If no direct match on PID can be found the process with the highest PID is selected and attached to.
If no match at all is found, the user is presented with a modal dialog telling him/her to start the process or cancel.
When trying to ReAttach to a process that is not running, the user is prompted with a dialog waiting for the process to start. This can for example be helpful to catch exceptions in the startup sequence of a web application running on IIS.