I know many people who come for help to me do this. It was easy for me to jump and say, 'Dude! I know how to debug!' but that would have been a wrong thing to do at that time. In fact, he thought that I don't know what is debugging and he explained me everything - all that Step-Into, Step-Over, Step-Out stuff with its shortcuts. 'Did you say debug?' He generously showed me how to do it. I hung up the phone, I walked to his desk and asked him. I knew for sure he was not asking me to switch my whole development environment to some remote machine sitting on the other side of the globe. I was a having a conversation with one of my coworkers on phone about a particular problem and he said, 'It will be slow but why don't you debug and see it?' My face turned red and I felt a little ashamed I knew what he was talking about. Don't let that distract you about what I am trying to say, just forget it and assume I have to test it on a remote machine that resides in the same Intranet. You may ask, 'Why don't you create a similar setup of that remote machine next to your desktop?' Trust me, there's a reason why I can't do it and I won't have a setup anytime sooner.

Every time I had a problem which is time-consuming to reproduce on my desktop I would log in to that computer remotely through VNC client, reproduce the problem, get the logs, diagnose, and test it again there. Of course, there is no connection with the geography except that the connection is slower. The importance of being able to debug a Java application that is deployed remotely, in another country or city, cannot be understated. Recently, I was working with a Java application that was bugging me when it was running in another country (USA), but it works fine when I run it on my desktop here in India.

Visual studio remote debugging port