Improve the Windows Phone emulators so that they can work within a Hyper-V instance
I currently use Hyper-V for various development environments within my enterprise. One pain point I have building Windows Phone apps is the fact that the emulator uses Hyper-V. This creates an issue when I'm in a Hyper-V instance. There are workarounds as documented at http://stackoverflow.com/questions/13148828/unable-to-create-the-virtual-machine, but I shouldn't have to follow a work around for what I would assume is a common scenario (common defined as more than 1% of developers not meaning majority).
Please vote for me!
Thank you for the feedback. The Windows 10 Anniversary Update (build 1607 / 14393) has included support for nested virtualization. (You can find more information here: https://msdn.microsoft.com/virtualization/hyperv_on_windows/user_guide/nesting). We are in process of enhancing the Windows emulators to work well in this nested environment.
Visual Studio Program Manager
It would be nice to be able to select an online emulator (e.g. for computers with low power). I guess MS is able to emulate a windows phone app session quite easily, and optimisations are much higher than on a single computer.
It would also allow to use many different ROMs as well as it takes a lot of disk space.
Make it possible, to select a remote host for running the Windows Phone Emulator, so you can develop phone apps inside a virtual machine.
Shawn Anderson commented
I agree 100% with this. More and more teams are moving all development to take place inside virtual machines. Being able to do mobile development inside a VM is key to help increase development in the mobile space.