Home Dashboard Directory Help
Search

Visual Studio 2012 Remote Debugger on Surface RT by Rudi Hansen


Status: 

Closed
 as Duplicate Help for as Duplicate


1
0
Sign in
to vote
Type: Bug
ID: 781188
Opened: 3/12/2013 4:33:39 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Visual Studio 2012 Remote Debugger not working on Surface RT
Details
Sign in to post a comment.
Posted by Microsoft on 6/21/2013 at 2:05 PM
I investigated another connect bug today, and while outwardly the issues seem very different, I think they are actually the same problem. I am afraid that what you are attempting to do is impossible with VS 2012, but we will attempt to address this in the next version of Visual Studio. The problem is that the remote debugger uses a communication technology that, by default, will attempt to validate the messages sent to the remote debugger are actually intended for it. The port forwarding that you are attempting to do will be blocked by this code. For the next version of Visual Studio, we expect to disable this check.

For Visual Studio 2012, you will need to find a way to make this work without port forwarding. All the various home routers that we have tested are able to exchange packets between the wireless and wired subnets without port forwarding. So hopefully this is possible on your router as well.

Again, sorry for the delay and for the issue.

Gregg Miskelly - Visual Studio Debugger
Posted by Microsoft on 6/21/2013 at 9:17 AM
Sorry for the long delay and I am not sure if you are still interested in investigating this. Are you still able to reproduce the problem? If so, from that error message, it sounds like you put the remote debugger into ‘no authentication’ mode. Did you also configure your project for no authentication mode?
Posted by Rudi Hansen on 3/22/2013 at 2:00 AM
What is the usual response time in this forum?
Posted by Microsoft on 3/13/2013 at 1:51 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 3/12/2013 at 10:46 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.