![remote debug visual studio winforms remote debug visual studio winforms](https://www.codewrecks.com/blog/wp-content/uploads/2012/03/image_thumb26.png)
Fortunately the manual configuration process is pretty well explained on MSDN sites for WinXP, Vista and Win7. Ideally Visual Studio and Remote Debugging Monitor should take care of the Windows Firewall settings after you run them with the elevated privileges, but life is life and you might need to get your hands dirty. Next step (the most boring and error prone in my opinion) is a network setup. Though you can debug 32-bit process in a 64-bit debugger. A caveat here: If your host is x86 machine, then you have no choice but x86 package for your remote computer – there is no way you can debug a 64-bit process in a 32-bit debugger.
REMOTE DEBUG VISUAL STUDIO WINFORMS INSTALL
There are two possible ways to install it – you can either download and run the setup package from Microsoft or copy all the necessary files from C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger (path on my 64-bit Win7). This listener is called Remote Debugging Monitor ( msvsmon.exe). Since the debugging process is wholly controlled from the host, there must be a listener on the remote computer that executes commands sent from Visual Studio.
![remote debug visual studio winforms remote debug visual studio winforms](https://www.codeproject.com/KB/debug/618804/index4-r-400.png)
I hope that this post will fill some of these gaps and will help you configure and run the remote debugging tools. After having read the MSDN documentation on this subject, I still missed some information. NET desktop application with Visual Studio 2010. I've recently needed to remotely debug a.