I own a Surface RT and I was programming in Visual Studio 2013.
I found the tutorial online on how to set it up but I couldn't do it. Right by the part Visual Studio tries to find remote connections it doesn't find the surface. If I reboot the surface, right about when I open the remote debugger there is a small (10 seconds) period where it becomes available on my Visual Studio to select but it disappears right after never giving me the change to remote debug the app.
Does anyone had this problem before?
You can try adding the Surface's address manually.
Right-click your Windows 8 project, select Properties, go to Debug tab. Here select Target device: Remote Machine and then in Remote machin field enter the address and port your Surface shows you when you run the Remote Debugging Monitor (in the very first message you will see something like Msvsmon started a new server named 'SOMEADDRESS:PORT'. Waiting for new connections.). This usually helps when Visual Studio fails to find the device on it's own.
Related
Earlier I asked a question, which has now been deleted. It was asked me of to come up with some different wording to my question. I'm sorry, but in this case I don't know how better to ask it then I have. Here's what I said:
At work I've got a desktop with Windows 10 on it. Been working there
for 3 years. We using TFS 2015 with TFVC. Recently I was given a
laptop, but without enough disk space, so what I have done is on the
laptop I mapped a drive to the second drive on my desktop, where I
keep all of the Visual Studio projects I work on, that are in TFS. I
had hoped I could just open the project on the mapped drive from the
laptop to the D: drive on the desktop. But VS complained to me. So, is
it not possible to open the same project, on only 1 machine, but being
accessed both on the machine and by a mapped drive from another
machine?
Perhaps it would be best if I illustrated. On my desktop I have a project in my D: drive, so it's located in D:\Src\LRAT. Its in TFS 2015 and we're using TFVC on-premise.
On my laptop I've mapped the drive from the desktop, using D: on the laptop, as D was available. So, I get into VS 2017 on the laptop and try to open the project in D:\Src\LRAT on my laptop. However, trying to do that results in a warning message issued from Visual Studio (the complaint I mentioned earlier) which says:
Team Foundation Server Version Control
The solution you are opening is bound to source control on the
following Team Foundation Server:
http://ourserver:8080/tfs/defaultcollection. Would you like to contact
this server to try and enable source control integration?
This confuses me a lot! I know that its in source control. Why is it asking me if I want it in source control? I want to be able to open it and use TFS/TFVC from my laptop against the same files and folders that are on my desktop. The dialog box that warning pops up in has 3 buttons, Yes No and Help. Clicking Help sends me to a very unhelpful link about Git and VSTS. I don't know what will happen if I click the Yes button, because that project on my desktop is already in source control, so I just click No because I don't know what else to do.
So, this leads to ask is it the case that in some way I don't yet understand opening a project created in VS 2017 and saved to TFS under TFVC on my desktop is different than opening that same project from my laptop connected to the D: drive on my desktop?
The solution you are opening is bound to source control on the
following Team Foundation Server:
http://ourserver:8080/tfs/defaultcollection. Would you like to contact
this server to try and enable source control integration?`
This kind of pop-up info, usually indicate there are some mapping issue related. Please double check your workspace mapping first.
Besides you could also try to connect your project in Team Explorer -Visual Studio follow below steps:
1 View->'Team Explorer'
2 'Manage Connections' (green plug)
3 'Manage Connections' (drop down) -> 'Connect to Team Project'
4 List of projects shows up from your account.
5 Select Project and Connect
More details take a look at this similar issue-- Opening an existing VS2015 solution bound to TFS hangs VS2017RC
I created a solution in Visual Studio 2015 using the Xamarin project type. During the initial creation, it did something to my network settings. I figured it was just doing what it needed to do to pretend to be an android phone or something. However, now every time I reboot my computer I have to go to my network settings and repair the connection or I can't use the internet.
Google search has so far been less than productive.
Does anyone know what I can do to permanently repair this issue?
so this required resetting my whole ethernet setup. I used this guide: Digital Citizen network reset guide. The gist of it is this:
Open the Settings App in Windows 10
Enter the "Network and Internet Settings" category
Select the "Status tab from the left-hand side.
Select the "Network reset" command from the page that's displayed.
You will be prompted to restart your computer. Click yes to all the options and make sure your work is saved. Restart your computer if it doesn't do so automatically.
I do not know if Visual Studio will mess this up again.
I have installed and registered Visual Studio 2010 Premium (+SP1) onto the Windows XP Mode VM within Win 7 Pro; I have applied all of the product updates also. I have not yet created any projects as my first task was to try and connect to our TFS 2013 Server.
My problem is that from within Visual Studio 2010 whenever I try to "Connect To Team Foundation Server" from either the Start Page; The 'Team' Menu drop down or the icon in the Team Explorer tab, the window to "Connect To Team Project" flashes up and immediately closes and so I cannot enter the details of my TFS server.
I cannot find any errors 'Event Viewer' and there is no further information from Visual Studio. It cannot be the TFS setup as I haven't got that far yet.
It looks like XP mode is interfering. Not all applications are supported and I have never seen or used visual studio in this manor.
You would be better either running VS2010 on your local Windows 7 or running it in a VM (Not in XP mode).
I found a solution to this and it is somewhat unbelievable, but it definitely worked for me:
Ensure HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Control Panel\Colors = 0
Go to Internet Properties -> General -> Colors
Change the check state of 'Use Windows Colors' and change the check state back again then click OK and click OK on the internet Properties page.
My "Connect To Team Project" window now stays open allowing me to select a server!
A colleague enlightened me to this trick which is regularly used for Win 7 installations but this is the first XP version (although it is the Win7 XP Mode VM).
This works to fix flashing pop up screens for Win7 & XP and has been reported to MS.
I could not get an emulator working for my target device and I wanted to debug a running program.
One-off setup
Connect the device to computer using ActiveSync. Basic connection is fine.
Do the following five steps the first time for each device (from http://msdn.microsoft.com/en-us/library/b1ksfbk7(VS.80).aspx)
On the Windows Start menu, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Remote Registry Editor.
Using the Remote Registry Editor, connect to the device.
Navigate to or create the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETCompactFramework\Managed Debugger
Set or create a DWORD value named AttachEnabled.
Set the data for the value at 1.
Also do the following the first time (from http://social.msdn.microsoft.com/Forums/en/vssmartdevicesvbcs/thread/5271dbc0-f4a0-422b-9ea3-3c4e9c99ace2)
Copy eDbgTL.dll and TcpConnectionA.dll from C:\Program Files (x86)\Common Files\microsoft shared\CoreCon\1.0\Target\wce400\armv4i\ to \Windows\ on the device.
To debug
Start the program on the device.
In Visual Studio, go to Debug > Attach To Process.
Select Transport : Smart Device.
Click Browse, select Windows CE Device, and click Connect.
From the Available Processes list select the program and click Attach.
I have installed the Visual Studio 2010 Remote Debugger on a Windows Server 2003 (x86) server, and am attempting to connect to it results in the following error:
Unable to connect to the Microsoft
Visual Studio Remote Debugging Monitor
named 'ServerName'. The Visual Studio
Remote Debugger on the target computer
cannot connect back to this computer.
A firewall may be preventing
communication via DCOM to the local
computer. Please see Help for
assistance.
I have checked my Windows firewall setting, and ensured file sharing is enabled on my local machine. I have ensured that DCOM is running on the server, as well as the debugging service. There are no actual firewalls involved that I know of.
What else do I need to change to get this to work?
I just ran into connectivity issue. The problem was the Client PC (my desktop) could connect to Remote Host running debug monitor, but the Remote Host could not send data back to my desktop.
Turns out that it was caused by the 'Profile' setup in Windows Firewall. The Firewall rule was being limited to 'Public' profile - but my desktop was connected to the local domain. Changing the setting to 'Domain' ensured the Remote Host could communicate debugging data back to Client desktop.
Check under Windows Firewall -> Inbound Rules -> Microsoft Visual Studio -> Advanced Tab.
Cheers,
J
Here are the steps I took to get remote debugging to work against an ASP.NET app. Not sure if you've done this already, hopefully something might help.
On my machine (call it DEVMACHINE from now on) I shared out the folder that contained the remote debugger (msvsmon.exe). On my machine, it was located at C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x86. I called the share msvsmon
On the server, I opened Windows explorer and navigated to \\DEVMACHINE\msvsmon, and ran msvsmon.exe (This opened the Visual Studio Remote Debugging Monitor)
On DEVMACHINE, I started Visual Studio 2010 and opened the solution that represents the application I'm attempting to debug.
In Visual Studio, clicked Tools > Attach To Process...
Entered the server name in the Qualifier field, then double clicked on the w3p.exe process that was in the list.
I then placed a break point in the location I wanted to start debugging
Couple things to note: The code deployed to the server was a Debug Build, the pdb files were there, along with the binaries. I had full admin rights on the server. No tools were installed on the server, I simply ran the exe that was located on DEVMACHINE. I did not have any firewalls between the DEVMACHINE and the server. And, both DEVMACHINE and the server are on the same domain.
Hope that helps.
I kept getting the same error listed above, and after trying all of the other answers, the problem turned out to be that DCOM was disabled on my development machine. The problem was solved by enabling DCOM using the instructions from this technet link.
I am using local DNS so I can test websites before they go live (by editing my hosts file).
I have a specific IP assigned by my router at home and at work.
i.e. dev.example.com is mapped to 192.168.1.123
When my machine changed to a different network without me realizing it could no longer reach the debugger and so I got the error.
Pretty obscure situation I had to get this error, which no amount of rebooting or recycling IIS will fix.
I had the same problems with the debugging service. The debugging service was starting automatically but I could never connect. I even turned off the firewall completely and that didn't help either.
Try running the debugging monitor (as opposed to the service) and connecting to that. You can find it in the start menu.
Confused about the difference between the monitor and the service? So was I. See http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/afc80afc-c8eb-4831-915a-1edb8d188f98
Same problem here. My reason was that Trend security was enabled in the local computer, and it was blocking the firewall. I could not stop it because I needed a password, so I just deleted all the Trend processes, and it seemed to work fine. So you could check if some antivirus is enabled that is blocking the access.
I also needed to add devenv.exe to the Allowed Programs in the Windows Firewall in the local computer, and set its policies.
Below is a quick step to set up Visual Studio Remote Debugging Monitor on Visual Studio IDE.
Open Programs > Microsoft Visual Studio 2010 > Visual Studio Tools > Visual Studio 2010 Remote Debugger Folder.
A Windows Explorer shows the 32 and 64-bit versions of the Remote Debugging Monitor.
Copy the respective ver that matches remote server (e.g. x64 machine use X64 folder & x32 machine use X86 folder) to a folder on
your machine.
While at the console on your remote machine, go to the folder and start msvsmon.exe.
Go to Tools > Options and change the Authentication mode to No Authentication and check the box Allow any user to debug.
From your development machine, on Visual Studio, go to Tools > Attach to Process.
Change the Transport to Remote and the Qualifier to the name of your remote server.
You should now see the executable, which you want to debug on that list. Select the process you want to debug and click Attach.
You may now debug the code while it is running on the remote server.
Just remember to turn off Remote Debugging Monitor at the remote server once done.
Please refer below MS link:
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-cpp?view=vs-2017