Hi Hank,
I had initially installed Windows Phone app stuff when I installed VS2013 on my new Windows 8.1 tablet. I didn't know, at the time, that there would be a problem with Hyper-V and VMWare. Imagine my surprise (and annoyance)!! I wrote a blog post about my experience after I got it all fixed:
http://geek-goddess-bonnie.blogspot.com/2014/07/visual-studio-2013-hyper-v-and-vmware.htmlWhat you're probably talking about is this command to turn Hyper-V on or off:
bcdedit /set hypervisorlaunchtype [off | auto]
Once I got it turned off, I did *not* want to mess with it again!
~~Bonnie
>Hi Bonnie,
>
>VMWare and Hyper-V are "one-at-a-time" -- or were when I had to google up a boot changer that let's me switch between having hyper-v set on, and not. I don't have the original reference, but it did work, and should be findable. It has to do (abstractly and imprecisely speaking) with who owns the hardware interrupt built into the CPU (the one that has to be turned on in the bios for hyper-v to work).
>
>hth,
>
>Hank
>
>>Pete,
>>
>>Viv has a good point about the lack of a XAML Designer in Xamarin ... I'm pretty sure they're planning on coming out with a Designer eventually, but I don't know where it is on their Roadmap.
>>
>>That said, what I've been meaning to play with for the last few months, but never seem to find the time, is to take the XAML I used when I wrote a little "test" Windows Store App several months ago, and see how much that XAML would need tweaking for use in Xamarin. My goal was to have an app for iOS and Android too, but I started with Windows Store because I could use a XAML Designer. Unfortunately, I cannot do Windows Phone at the moment until I figure out how to get around the Hyper-V requirement (we use VMWare and the two are incompatible on the same machine, AFAIK).
>>
>>Anyway, I think I will try playing with that XAML this weekend and see where it gets me ....
