In the Commands window we can manage our existing commands, and create a new one with the Add button. The same thing happened to VS macros with Visual Commander, a freemium VS extension that lets us reuse existing VS macros, and create commands and extensions using C# or VB.NET.Īfter installing the extension, you can open the Commands windows with the VCMD->Commands option. I really like it when a popular feature of a product is removed, but the community brings it back. “Macros are no longer available in Visual Studio 2012.” However, the first comment on the answer destroys our happiness:
This approach is described in this Stack Overflow answer, it seemed very straightforward and promising. The first approach I found is to write a Visual Studio macro that looks for a specific process and attaches VS to it. So I started looking for a more convenient way to attach to a specific process quickly. This method of attaching to a process is OK if you have to do it only once in a while, but if you have to debug applications this way regularly, it becomes time-consuming to search for the process in the list every time. This can be done with the Debug->Attach to Process… option, where we have to select the desired one from a list of all running processes. It’s a very useful feature of Visual Studio that besides starting an application for debugging, we can attach the debugger to already running processes as well. visual studio debug tooling visual commander.Attach to specific Process shortcut in Visual Studio
0 kommentar(er)
