Thursday, October 2, 2014

Visual studio remote debugging symbol files location

Visual studio has a great facility to do remote debugging which is a lifesaver in many cases where our code works at one location but then fails to run properly at some other location. However, we need to be careful while using the remote debugger components. I have listed the major points to consider below:


  1. There are two separate debugging tools for x86 and x64 environmets
  2. Remote debugger on the remote machine needs to be run with the same user account as the user account used to run visual studio on development machine. (There is an option to relax permission settings and allow any user to debug, but when I tried to use it, it didn't work for some reason.)
  3. Debug symbol files (.pdb) location is very important, since visual studio has to be able to locate these files on local as well as the remote machine. The rule of thumb in this case is to place them at the same relative location on both development machine and the remote machine. A detailed explanation can be found in this post http://www.wintellect.com/blogs/jrobbins/visual-studio-remote-debugging-and-pdb-files


No comments:

c# httpclient The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch

 If we get this error while trying to get http reponse using HttpClient object, it could mean that certificate validation fails for the remo...