I am working on project. I have taken remote system. My problem is that Visual studio and windows phone 8 device located in remote place. Windows phone 8 is connected in remote server. All sources and devices are located in remote server. I need to test and debug the app. How can i see the device screen? I want to control the device using remote server. Any software or method to take control the phone in PC?
In other words, I want to control or display the screen of windows phone 8 device on PC.
Any idea should help me a lot.
Thanks in advance.
As there is not a way to interact with a physical Windows phone 8 remotely yet (unless you are a Microsoft employee with special access to private builds of the phone), I'd suggest that the remote site set up a machine configured with Windows 8.1, Hyper-V, Visual Studio for Windows Phone, and the emulators. You can use Remote Desktop to gain access to the machine and test and debug the application through the emulators.
Or, of course, the best would be if you could just gain access to the source code for the application and do the testing locally. Depending on the resources required by the application, you may need to create a LAN to LAN VPN in which all traffic would route through the remote site.
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.
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.
I have been trying to deploy visual studio Apache cordova tool project on window phone emulator but i am getting the following error.
windows phone emulator wasn't able to connect to the windows phone
operating system the phone didn't respond to the connect request.
When i click okay the Additional tool(>>) icon is not enable. and there is no internet on the emulator.i have remove and re install Hyper-V but is not seem to be working. I am in a Domain network with DHCP.
can you install the Windows Phone virtual switch in Hyper-V Manager and let us know if that resolves the issue?
I think this is a straightforward question but I'm looking for someone who has actually tried this and can say yea/nay.
I want to run the Windows Phone 8 emulator on another Hyper-V host than the Visual Studio machine, and connect to it as a debugging device. It would be similar to connecting to a "real" phone in that it's not a local VM, but would obviously not be through a local USB connection.
Do the development tools for Windows Phone 8 support this scenario?
Do the development tools for Windows Phone 8 support this scenario?
No, this is not supported in the public SDK.
I have developed a windows phone application that makes use of mspn service. Its working fine with windows phone emulator. Now i wish to test it in a windows phone device. I have a windows phone device with me. What are the various steps in testing my app in a windows phone device. What are the main differences between testing my app in windows phone emulator and real device?
The major difference between testing on the emulator and a real device is performance, I have been bitten by this one - it all runs fine on the emulator on a powerful desktop machine, but crawls on the real device.
To test on a real device you have to sign up as a developer at the Microsoft AppHub (http://create.msdn.com) and pay your $99 - you can then unlock your phone, so you can load your app onto the phone using Visual Studio and Zune.
HTH - Rupert.
Additional to the performance gap, testing in a real windows phone device shows you how your app will behave in a real scenario.
I've found that reliability of internet connected apps decreases a lot on the real device, because of many factors. You will see triggered a lot of network-related exceptions, dns, and timeouts that your emulator couldn't see. Its a very healthy practice to test in a real device.
First of all you need your device to be "developer unlocked". You can do it by signing up to the Microsoft App Hub. If it happens that your country it not listed under the App Hub Developer program, it's not the end of the world. You can sign up with a global publisger that will give you access to the app hub under limited priviledges. I name a few ones:
Region / Name / Web Site
APAC App Port http://www.app-exchange.com
CEE APPA Market http://appamarket.com
CHINA MTel http://wp.mtelnet.com
CHINA Device7 http://www.device7.com
MEA Yalla Apps http://www.yallaapps.com
After you develop unlock your device you only need to plug in your device and visual studio will recognize your phone.
So, next to your debug button you will be able to chose between Windows Phone Emulator and Windows Phone Device. Just run and visual studio will deploy your app into your device.
Last but no least, make sure Zune software is open. And you phone screen is unlocked.
You will be surprised on how easy is to make in-device debugging.