I realize this is somewhat "bleeding edge" given that Win10 is still in preview... but this worked using 10061 and CTP6 so I'm hoping I can get it working now with 10074 and RC1...
My goal is to able to run the Windows Phone emulators inside of the Windows VM. I don't care about the Android emulator - I can run the Xamarin Android Player emulator on the Mac host and connect to it from within the VM using "adb connect" (this works perfectly fine).
I am using Parallels Desktop 10 for Mac, fully updated. My VM is Windows 10 Preview, Build 10074. The VM was created from scratch. I have Visual Studio 2015 RC1 installed (from ISO - the web installer has lots of problems) with all mobile development tools selected. I can see that the features are installed - they all appear in Add/Remove Programs.
However when I attempt to launch the Windows Phone emulator from Visual Studio (F5 to launch, deploy, and debug), I get an error that says Hyper-V is not enabled. I *do* have Nested Virtualization enabled in the virtual machine configuration. As mentioned above, this configuration was working on the previously released previews of Win10 and VS.
Any ideas on what I can try to fix this and get the emulator working?
My goal is to able to run the Windows Phone emulators inside of the Windows VM. I don't care about the Android emulator - I can run the Xamarin Android Player emulator on the Mac host and connect to it from within the VM using "adb connect" (this works perfectly fine).
I am using Parallels Desktop 10 for Mac, fully updated. My VM is Windows 10 Preview, Build 10074. The VM was created from scratch. I have Visual Studio 2015 RC1 installed (from ISO - the web installer has lots of problems) with all mobile development tools selected. I can see that the features are installed - they all appear in Add/Remove Programs.
However when I attempt to launch the Windows Phone emulator from Visual Studio (F5 to launch, deploy, and debug), I get an error that says Hyper-V is not enabled. I *do* have Nested Virtualization enabled in the virtual machine configuration. As mentioned above, this configuration was working on the previously released previews of Win10 and VS.
Any ideas on what I can try to fix this and get the emulator working?