Since installing the Windows 10 Mobile emulator 10.0.15063 under VS 2017, I can no longer connect to the Internet from the emulator. I didn't have this problem with the Windows 10 Mobile emulator provided with VS 2015.
It seems that the problem comes from setting up the virtual network adapters created during the installation, and the Internet connection mode of the PC hosting the Hyper-V machines (I am connected in WiFi). I can't change the settings correctly (and on the other hand, is it normal to have to edit them?). Thank you to the one who can help me.
Related
I'm developing a UWP app for Windows 10 Phone. Since some days when I try to deploy the app from within Visual Studio I get asked for a PIN in order to connect to the device
In the phone settings I can trigger pairing so a new PIN is generated for me. But when I enter that PIN, a new dialog appears telling that the PIN was wrong:
If I press 'Cancel' then the deployment is interrupted with an error message:
1>Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
It's strange but some days ago I was not asked for the PIN when I deployed the app. :-( So currently the only option I have is deploy via the web portal. This works but it's enormously slow :-(
Can someone tell me how to solve the problem or what PIN should I enter in order to achieve the deployment?
I had this problem today, closing visual studio and restarting IpOverUSB service fixed this issue for me.
You might want to take a look at Ricardo Pieper Question he has listed all the things he tried to do and all the things that might work.
It looks like the problem was caused by the fact that I'm developing inside a virtual machine (VMWare Fusion on Mac). After setting up the development ebvironment on a PC the deployment works fine.
I can even debug the app running on the phone from inside Visual Studio.
Here's a solution which worked for me:
I had the same problem on my Macbook running VMWare Fusion and trying to debug on my Lumia 950 phone. I was nearly giving up, then I tried using the free VirtualBox and with a virtual USB 3.0 port (which requires the VB extension pack). And it worked!!
Here's my setup:
VirtualBox 5.0.14
VB Extension Pack
Win 10 Development VM from Microsoft – the VirtualBox variant, Build 201601: https://dev.windows.com/en-us/downloads/virtual-machines
Lumia 950 with Windows 10 Mobile 10.0.10586.29
In the VM, I configured to use the USB 3.0 port, since with USB 1.x the phone device driver could not be installed by Windows 10.
The VM contains Visual Studio 2015; I created a UWP JavaScript application and ran it with "Debug" on the connected Lumia device.
Had to go to the Developer options on the device.
Switch back to "Windows Store Apps" option, and then back to "Developer Mode"
I am not able to start any of the Mobile Emulators for Windows Phone 10 (version 10.0.10240).
When I start it from the VS 2015, it gets stuck at "OS is starting". In the Hyper-V Manager, I can see the status "Starting (10%)" for the whole time. After some time, the machine is automatically restarted and it gets stuck at "Starting (10%)" again. Then it timeouts again and the emulator shows an error: "The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does not exist". That is weird, because I do have the rdvgm.exe in the C:\Windows\System32.
I have seen that there are some questions with the same error, but they are resolved by fixing the network switch or by killing devenv.exe after it shows "OS is starting". I have tried both, but it did not help. The network switch issue is different (I have seen it on a different computer - in that case the emulator starts correctly, but VS is not able to connect to it). I am stuck at "Starting (10%)".
What can I try to get it working? Windows Phone 8 emulator is working without any issue.
Thanks
The problem was that Hyper-V detected a graphic card which is able to work with RemoteFX (integrated Intel GPU) but the dedicated one (AMD Radeon) was not supported. I was not able to convince Hyper-V to ignore the dedicated one. When I disabled the RemoteFX support for Hyper-V (unchecked it in the Intel GPU setting in the Hyper-V configuration), it started working.
I found this Microsoft technical support desk yesterday. Its an on line chat with their technical people. I don't know if it covers all MS products. I was asking them about Outlook. Could be worth a try. I found it a touch slow at times, but ...
https://www.awasa.microsoft.com/en-GB/consultation/index?id=914801398064643&skuId=0
Hyper-V has problems enabling RemoteFX with some dual gpu graphics cards. Disabling one of the graphics cards in device manager solved the problem for me:
Disable one of the integrated graphics cards in device manager. I disabled Intel (R) HD Graphics 4600 and left NVIDIA GeForce GT 740M enabled.
Reboot Windows.
Delete the existing mobile phone virtual machines in Hyper-V Manager.
Start Visual Studio and deploy your app again.
I'll be honest, with much distress, I performed a complete factory reset. Reinstalled only Visual Studio 2015 Community edition (only with the tools I needed and not any other emulators such as Android), and it worked after setting up Hyper V as instructed via documentation on dev.windows.com
My Visual Studio 2015 Enterprise doesn't launch the emulator, however I am able to run it manually from the Hyper-V Manager. When run it from the VS after ~7-8 mins I get the following error:
"Windows Phone Emulator is unable to connect to the Windows Phone operating system:
The phone did not respond to the connect request.
Some functionality might be disabled"
What might cause this problem? I am running Windows 8.1 on Fujitsu LIFEBOOK E744
My case is slightly different than suggested duplicate as my notebook is in a corporate network and I am not able to turn off firewall nor stop any network monitoring software.
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'm playing around with windows phone 7 development, when I press F5 Visual studio takes forever to deploy the app, I get
Window Phone Emulator is doing complete OS boot.
What would be the problem?
PS: I'm using windows 7 on Mac with Parallels Desktop
The emulator isn't supported running inside or side by side other VM's at this stage. It is implemented as a VM itself. VM's running on windows platforms will be detected by the emulator startup and a specific error message provided. I've noticed several people having the same issue from Parallels on Mac ... presumably the VM detection doesn't work over there to stop the attempt.
System requirements documented here and here for your reference.
Similar to how we have to run a Mac to develop for iPhone without hassles, you'll need to run a PC to develop for Windows Phone 7 - at least for now.
You may also find your issue with the WIndows Phone Emulator is because the Emulator actually the real phone ROM running in a Virtual Machine.
Since your situation is a VM (Windows 7 on Parellels on Mac) this may explain your performance issue. Developers using VMWare have had similar issues plus Virtual PC / Hyper-V does not support Windows Phone 7 at all.
Running virtual machines on virtual machines is a massive performance hit, your only solution may be a cheap PC installation of Windows Phone 7 tools etc on compatible hardware ie Graphics Card / with WDDM 1.1 compatible drivers etc.
For my WP8 deployment, I notice that disconnecting my MacBook Air from the power source will slow the deployment down considerably (so will the debugging and tracing).
Simply plug the laptop back to the power source and everything will become fast again.
Don't kill the emulator between debug sessions. There is no need.
Also - Visual Studio 2010 Express For Windows Phone, which is installed with the tools, is much more responsive as it has less features running.
So if speed is really an issue, that may be an option.