Search

Can't remote debug on my Surface-RT by Gábor Mánich

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
to vote
Type: Bug
ID: 773465
Opened: 12/4/2012 2:53:20 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have a Surface-RT device and try to debug my application on it. I have installed Visual Studio Remote Debugging tools on Surface and configured them.

In VS2012 (both machines DevPC and Surface are on same Wifi network) I try to locate my surface but VS2012 is unable to locate Surface. If I enter IP address to my surface and try to debug the application on surface I get following error: "Error: Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named '192.168.1.111:4016'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."

I checked firewall, disabled authentication, nothing helped. Any ideas what shoud I do?

Thanks,
Gabor Manich
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Load project in VS2012 and start debugging on remote machine.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Can't remote debug on Surface-RT

Expected results

Be able to remote debug on Surface-RT
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/28/2013 at 1:06 PM
Hello Gabor,

Can you let me know what version of the VS client and what version of the remote debugger you're trying to use? I'd recommed using the update 1 version of the remote tools http://www.microsoft.com/en-us/download/details.aspx?id=30674. It should be compatible with both the RTM and Update 1 version of the VS client.

Let me know.

Marc Paine
Visual Studio Debugger QA Lead
Posted by Microsoft on 12/5/2012 at 1:09 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 12/4/2012 at 3:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.