When a device is on a remote location (so not within the local network), how can I deploy an application to the Windows 10 IoT device from within Visual Studio? What ports need to be forwarded in the router. And second, (quiet important actually) how would the authentication work? When Windows Authentication is selected, does it use the current windows user? I would expect to be able to provide credentials that are set from within the web dashboard of Windows 10 IoT.
The port used to deploy an application by Visual Studio 2015 is 4020 assigned by default. You can set a different port number of you like in Visual Studio Remote Debugging Monitor. Also, you can choose permissions to add or remove users that have permission for remote debugging.
For Windows IoT device you can select your device in IoT Dashboard and right click and select "Open in Device Portal". Then you can enter credential information.
In Debugging of Device Portal, you can start Visual Studio Remote Debugger if "msvsmon.exe" is not in Live process dumps list.
After that, you can deploy your app within Visual Studio using "<your device ip address>:<port>" as remote machine name. You can find "port" number after starting Visual Studio Remote Debugger like this:
You will be request to enter remote debugging PIN after deploying. This PIN you can edit in Home page of Device Portal like this:
More information about credentials processes in Windows Authentication you can reference here.
Related
I'm trying to deploy a UWP app from my Alienware 18, Laptop with Windows 10, version 1803 to a Tablet Galaxy TabPro S with Windows 10 version 1803 as well.
I had activated developer mode on the device target and the USB device discovery option as well.
First I tried connecting a USB Cable from my laptop to the tablet which has a USB-C port.
But My laptop doesn't even find it.
What I want is to find a way to deploy a UWP from my laptop to the tablet, I made some research and I found out that, only HoloLens and Windows Phone 10, are findable using USB Connection.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
I would appreciate details because I tried to follow remote deploying but I haven't been able to successfully find the tablet.
The Windows 10 on your tablet, just like on your development machine, supports remotely debugging over the network rather than over USB. Make sure both machines are in developer mode, with the other machine also having Device Discovery turned on as described here. Both should connect to your WiFi as a private network. After that it should be as simple as configuring your project to deploy to the other machine, rather than locally, as described here and here. Don't forget to pair them with a PIN.
If you host a web API on your development machine, configure your firewall as described here.
Use remote debugging over at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2017
Make sure you follow the instructions, sometimes remote debugging is barred by firewall so check that.
Alternative right click your main project, go to store then click create packages for sideloading and then send the package over at your Samsung device.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
To run a UWP app on a remote machine, you must attach to it using the Remote Tools for Visual Studio.
In some scenarios, the remote tools are automatically installed when you deploy to a remote device. For example,
For Windows 10 PCs running Creators Update and later versions, remote tools will be installed automatically.
Then, your remote device and the Visual Studio computer must be connected over a network or connected directly through a USB or Ethernet cable. Debugging over the internet is not supported.
After that, you need to configure the Visual Studio project for remote debugging. In the properties of the project, select the Debug and choose the Remote Machine from the Target Device list. In general, I will input the remote machine's IP address, you could choose Find to choose the device from the Select Remote Debugger Connection dialog box.
Next step, please move to your Tablet, you need to Set up the remote debugger. You must have administrative permissions on the remote computer. Then, open the Start menu and search for Remote Debugger. If you could find it, just start it normally. If you cannot find it, you need to install it Remote Tools manually. See this link to Download and Install the remote tools. Once the Remote Debugger started, you could do some configurations. After that, you could choose Start Debugging on the Debug menu (Keyboard: F5). The project is recompiled, then deployed to and started on the remote device. Please read Run UWP apps on a remote machine in Visual Studio for more information.
I've been unable to get Visual Studio, running on my development machine, to successfully deploy to a Surface Book on my local network. Error message is included below. On the Surface Book I've installed Remote Tools for Visual Studio, and set up Developer Mode. VS on my development machine shows me the SB, and allows me to select if from a list of deployment targets, including it's Authentication type, but deployment fails.
There is a "pair" option on the SB, which I haven't been able to make work & I'm not sure if it's necessary. In addition, I saw a post saying this option (local network) was no longer supported. Is it still supported, and if so, any idea what I'm doing wrong?
Error Message:
Error DEP6957: Failed to connect to device '10.0.0.179' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. COMException - Error HRESULT E_FAIL has been returned from a call to a COM component. [0x80004005]
To remote debug a uwp app, we should install the corresponding version Remote Tools for Visual Studio, before we can deploy the app to the remote device, we should configure the Remote Debugger tool. See the Run UWP apps on a remote machine in Visual Studio for details.
For your this issue, it should be you select the Windows authentication mode in your Visual Studio as the follow image, but you don't have access to the credentials of the signed-in user of the target machine. In your VS, you should use the credentials of the signed-in user of the target machine to deploy your app when the VS popup the permission window. See the Authentication modes to learn the differences.
On the other hand, you can also try to use the None authentication mode to remote deploy your app as the following steps.
Firstly, in the Visual Studio Remote Debugger of the target device, select Tools=> Options to configure the options Window as bellow,
Then in your Visual studio, right click your UWP project=> properties=> Debug to cofigure it as None authentication mode.
The answer from Breeze Liu was very helpful, and got me most of the way to the solution. The final step that I was missing was to add my account to the Remote Debugger's permission list. It's found at Remote Debugger>Tools>Permissions. I had to add my account on the target machine to the list of "permitted" debuggers.
I am trying to debug an app, using Visual Studio 2017, that I will run on a virtual machine I've set up on my development system. The virtual machine runs Windows 10 (as does my development system).
I've installed the latest VS 2017 Remote Tools package on the virtual machine, and configured it. It is happily running on the virtual machine...but I can't connect to it from the desktop system.
When I do an attach to process, and a Find to find the system, the virtual machine is found.
However, after selecting the virtual machine, I am prompted for credentials. I've tried using the same login credentials I use to log onto the virtual machine, but that doesn't work. And there's no information shown as to what might be the problem.
The virtual machine is running under Hyper-V.
How do I go about setting up a remote debugging connection to virtual machine running on the same system where I am running VS 2017?
I ran into the same issue and managed to get it working, after much effort.
First, try switching the debugger authentication mode to "No Authentication" (Tools -> Options) and setting your project in Visual Studio to match (see the language-specific links in the MS docs link below). That will help you determine if it is a credential issue or something else.
The microsoft docs say, "You can run the remote debugger under a user account that differs from the user account you are using on the Visual Studio computer, but you must add the different user account to the remote debugger's permissions."
In my case, I ran the same account on both machines AND added my account to the debugger's permissions, and it still didn't work. We use Azure AD, and I was using a domain account. My VS computer was on the domain, and the VM was not (even though I could sign in with a domain account). After adding the VM to the domain, I could connect with "Windows Authentication" enabled in the debugger settings.
I'm trying to set up remote debugging across domains. My Windows 7 workstation running Visual Studio 2010 is on one domain and I'm trying to debug an ASP.NET app running in IIS 7 on a Widows 2003 server box in another domain. I have found many instructions on how to set this up, this being the best, most clearly written one: http://blogs.interknowlogy.com/2011/11/16/remote-debugging-from-visual-studio-2010/
However, I can only seem to connect to the remote debugging monitor on the server if Visual Studio is being run as the local user on my workstation, not as the domain user. This creates a number of challenges, such as loss of source control connectivity. When I try to connect using the domain user I get the following error: "Unable to connect to the Microsoft Visaul Studio Remote Debugging Monitor named 'username#servername'. The specified account does not exist." (I have substituted a generic username#servername for the actual values)
I have found a number of sources suggesting this will work with the domain user running VS2010 but have had no luck. Any idea what I might be missing?
Solved
First, i've read #KyleMit's answer on the same question and done all steps.
But, for across domain debugging also need to edit C:\Windows\System32\drivers\etc\hosts file on local computer.
Just add remote computer's ip address like this:
172.172.172.172 SRV-TEST-ADRESS
Where:
172.172.172.172 - ip address of your remote server
SRV-TEST-ADRESS - Server's name from Visual Studio Remote Debugger
Monitor on remote computer
You can know your server's ip address by ipconfig in cmd
After that, i could attach to proccess on remote computer across domain.
I have a c++ program running on a remote machine.
I'd like to debug it from my machine.
I've installed remote debugging services (msvsmon.exe ) on the server.
Firewalls are not active not in the client nor in the server.
The program is running on the server (.pdb file is also there).
In the client I open the project in VS2010 , I go to debug->attach to process.
In the qualifier field I copy the value of the server name in msvsmon.exe.
When I hit enter, I get an error prompt saying :
"Unable to connect to Microsoft Visual Studio Remote Debugging Monitor named Administrator#TESTER1, the requested name is valid, but no data of the requested type was found"
In the server, the Authentication mode in msvsmon.exe is set to Windows Authentication.
Any help will be much appreciated.
Regards,
Omer.
Take a look at:
How to: Set Up Remote Debugging from Microsoft
Remote debugging with Visual Studio 2010 from CodeProject
In your case, take note of the suggestions regarding native debugging and windows authentication.
In my experiences with remote debugging a machine that is on my local network, I bypass windows authentication and setup the remote msvsmon.exe to allow anyone to connect to port 4015. So, then in the 'Attach to Process' dialog I select Transport > Remote (Native only with no authentication) and for the Qualifier I enter TESTER1:4015 or TheIPAddress:4015 if the name of the PC cannot be resolved.