Skip to main content

How to setup remote debugging on a remote machine running within a VM?

This guide will show step-by-step instructions of setting up a remote machine for remote debugging using Visual Studio 2013

Prerequisite:


  • Visual Studio 2013 or later
  • Remote machine running Windows 7 within a VM player
Note: Since Visual Studio 2012, Microsoft only supports remote debugging for Windows 7 or newer. To remote debug Windows XP, you'll need to use an older version of Visual Studio and its respective remote debugging tools.


 Step-by-step guide:

  1. Download and copy the Remote Tools in your Win7 VM.
    • You must get the update version of the Remote Tools for Visual Studio 2013 that matches the update version of your Visual Studio installation.
  2. Install the Remote tools in your VM.
  3. After installation, run the Remote Debugger 
    1. Navigate to Tools->Options Menu
    2. Ensure that Windows Authentication is selected. Press OK.
  4. Open Visual Studio in your local machine.
    • Make sure you have setup the remote machine in the project you like to remote debug as shown in the following figure.


  •  You also need to update the Output Path of the build so that it matches the path in your     remote machine.


Important Notes:
  • You must have the same version of the code on the server as you have locally, so make sure you publish your solution before trying to debug it.
  • You must publish the Debug version of the code to the server. If you publish the Release version, the .pdb files which contain all of the debug symbols will not be included and you won’t be able to debug remotely.

5.  From Visual Studio in your local machine.
    1. Navigate to Debug->Attach to Process
    2. Ensure in Transport field "Default" is selected
    3. Type your remote machine IP or alias in the Qualifier field and click Refresh button.
    4. If prompt for authentication type user name and password for the remote machine
If the connection is successful it will list all the running process in remote VM machine





6. Select the process you like to attach for remote debugging and click Attach.


Congratulations now you can remote debug to the attached process!



Things to check In case attaching to process fails:

  • If process attaching fails with VS 2013 showing the message "Unable to attach to process. The RPC server is not available".
  • Ensure that "Use Manage Compatibility Mode" option from Debug -> Options and Settings ->General Tab is unchecked.
  • Ensure Firewall is not blocking VS to attach to the remote process. Add VS 2013 in the list of allowed firewall program.
  • Make sure that RPC service is running both in local and remote machine.

Comments

Popular posts from this blog

Creating dynamic email templates using C# and Office Outlook

It is quite common for many applications to send automated email notifications. Couple of months ago, I have worked on improving our old email template format to make it more user friendly.
In this tutorial I will walk you though regarding how I took advantage of Microsoft Outlook to quickly generate custom email template and later using the html template for building an automated custom email application using C#.

Steps:Creating Templates: Using the rich text editor support  in Outlook create a nicely formatted email. Use placeholder text for the values you like to change dynamically based on your task completion status.

To keep this tutorial simple, I have created a  simple table with placeholder text inside the third bracket [place holder text]. However, you can use anything supported by outlook editor.Getting HTML code: Send the created email to your own address. After that, open the sent email and right click to view source. It will display the HTML source of the email body with …

Book Review - The Phoenix Project

Here at Skybox Labs, we do regular lunch and learn session where a fellow colleague present on topics ranging from clean code, continuous integration, game development, machine learning to almost any areas where there are reasonable interests.

One of the very recent lunch and learn series that I have attended was focusing on DevOps which got me interested to learn more about the topic. I was looking for recommended books and the lead presenter highly recommended that I start with 'The Phoenix Project' by Gene Kim

Being inspired by the stellar reviews in Amazon, I have decided to get a copy and read it over the weekend.
A fantastic book that contains a wealth of information and delivers it in an intelligent and interesting way; a story. The book successfully captures the events and struggles of most people who work in IT Operations and gives a very good explanation on why these problems exist, and how you can solve them. It portrays a very effective way of thinking in applying …

Interesting bug - Line endings and Hash Code

I recently came across an interesting bug which emphasize how different line endings format can break your custom equality implementation if you do not carefully consider them.

Context
We have an application that periodically updates the local assets with latest updated resources. In a nutshell, it makes an web api call to get the latest set of metadata and compare them against a locally stored metadata file. If they differs then we update the locally stored metadata file and download new/updated resources.

Bug
For a particular asset, associated metadata file was always getting updated although there were no visible changes detected using the revision history.

Investigation
My obvious suspect was the code responsible for doing the equality check between local metadata and the metadata received from the Web API.

For verification, I setup a conditional break-point which will be hit when the equality returns false. After my debug hit the break-point, I looked into all the properties and fou…