For most developers, debugging an application means setting a breakpoint with F9 on a line of code, and then pressing F5 (or Debug | Start Debugging) and stepping into and over statements with F10 and F11.

The experience is great when you're debugging code on your local machine, but what if you need to debug code running on a different machine and Visual Studio isn't installed on that machine? This is where remote debugging tools come into play.

Even though many developers aren't aware of this functionality, debugging code on remote machines with Visual Studio isn't anything new. It's just that until now, the debugging experience has been limited and unrefined. With Visual Studio 2013, the experience is much improved, and combined with speed improvements and an increasing range of devices that applications need to run on, remote debugging is something every developer should know.

This recipe shows how to configure a machine for remote debugging and then...