- #THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR UPDATE#
- #THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR PRO#
- #THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR SOFTWARE#
- #THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR CODE#
I'll give you a quick run through of the steps I followed:
#THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR PRO#
My development machine (lets assume this had a name of DEVMACHINE is running VS2012 and I'm trying to debug an application on a Surface Pro 2 (lets assume this had a name of REMOTEMACHINENAME. I was getting the same error but under slightly different circumstances.
#THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR UPDATE#
With VS2013 Update 2, what files and folders go where, and do I or VS2013 put them there? Am I understanding what VS2013 Update 2 is offering in terms of remote debugging? So am hoping to get scenario 1 working where VS2013 does some sort of publishing. Currently I cannot test scenario 2 since I am connecting using OpenVPN, and my server does not directly see my local desktop. Implies it will publish the files on the remote machine and to do a "Start project" as you would normally do. I know the older remote debugging (scenario 2) used "start external program" which linked to files back on the local machine, but it seems VS2013 Update 2 enhanced this and this doc remote folder locations are reversed from what I would expect with this new update (scenario 1). The remote monitor is started and tells me I connected each debug attempt so this is not a connection issue. The system cannot find the file specified."Īnd my local executable is at the path mentioned. "Error while trying to run the project: Unable to start the program '\.exe'. It surprised me that the working directory folder was actually required on the local machine else I got a complaint it was missing, and now, I get the error Then modified the local VS2013 project to use remote debugging specifying the remote machine name and a C:\RemoteDebug working directory folder. Please remember to mark the replies as answers if they help and unmark them if they provide no help.I have VS2013 Universal Update2 on my Win7 圆4 desktop and am trying to debug a process that needs to run on the server so installed the visual studio 2013 remote debugging monitor (the 圆4 Update2 version) on my Windows 2008 R2 圆4 server.
#THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR CODE#
MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Verify that the remote machine is accessible on the network. Remote Server Name is correct in the Name box in theģ. Make sure the Remote Debugging Monitor is installed and running on the remote machine. “Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named "name".”ġ. If you get this issue, you need a 64-bit version of Windows and run the 64-bit version of msvsmon.exe first.Ģ.
#THE MICROSOFT VISUAL STUDIO REMOTE DEBUGGING MONITOR SOFTWARE#
Check your computer's system information to see whether you need an x86 (32-bit) or 圆4 (64-bit) version of the program,Īnd then contact the software publisher. “The version of this file is not compatible with the version of Windows you're running. However,Įven after doing so, you might see the following error message: To fix this problem, before you start debugging the dump file, run the 64-bit version of msvsmon.exe from %ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\圆4. Please remote debug with the 64-bit version of Visual Studio Remote Debugging Monitor (MSVSMON.exe) instead.” “The 32-bit version of Visual Studio cannot debug 64-bit processes or 64-bit dumps. Note: I want to debugg the code remotely.ġ. When I try to attach to process I get the following error if it is running as This does not allow debugging of Win64 processes.ĭo you want to continue? (Use /nowowwarn to suppress this warning)īut when I try to attach to process I get the following error. This is the Win32 version of the Remote Debug Monitor. While starting the "Visual Studio 2008 Remote Debugger" at server, it gives the following warning: To do that I tried installing "Microsoft Visual Studio Remote Debugging Monitor " as I want to debug the event handler that I had written. Windows Server 2008(32 Bit).īut my Project Server is Installed in Windows Server 2008 R2 Enterprise(64 bit). I am trying to create a Eventhandler for Project Server 2010 using Visual Studio 2008 which has