Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.
Talk:Windows Phone 8 Emulator in a Windows 8 VHD
Hamishwillee - Subedited - thanks for this article
Hi Pengguang Wu
Thanks for competing in the competition. I have just subedited the article to improve the English and wiki style a little (to some extent this was personal taste). The most important change was the warning up the top - Microsoft explicitly don't support this use case so it is important to make that very clear to users "use at your own risk".
A couple of issues:
- This states that you can't run the Emulator in virtual machine, but this entry shows how to do it Windows Phone 8 SDK on a Virtual Machine with Working Emulator. That doesn't mean this isn't useful, but we should remove that note.
- The article is fairly simplistic in that it deals with the fact that some computers don't support Windows 8 by limiting itself to recent computers. A better approach would be to outline some preconditions, as in Windows Phone 8 SDK on a Virtual Machine with Working Emulator - that way people can confirm whether this will work for them in advance.
- It would be great if you could add an image for step 2 ( check if the hypervisor is enabled in Windows 8)
- Given the warning above, did you have any performance issues.
- I would have a second section "Removing the VHD" with instructions on how to remove the boot entry.
- The title isn't quite right, because it doesn't differentiate between Windows 8 running inside a virtual environment and one that is just booted from a virtual disk. How about "Windows Phone 8 development on Windows 8 booted from a VHD"
Thank you for this. I'm not sure it will suit everyone, but its good to describe the option as long as its limitations are documented.
02:50, 8 November 2012 (EET)
Pengguang Wu - Reply to your comments
To address your issues specifically;
- The entry is only for a subset of PCs capable of hyper-v in a client OS bought recently such as Windows 7 and for people who are comfortable with setting up multiple booting systems. It is not intended for everyone (neither are other articles). If you intend to upgrade to Win8, this entry does not apply. On the other hand, if you just want to kick tires, this entry shows one way to do it without additional monetary cost other than your curiosity and time. You do not have to sacrifice your current paid OS to do so. You can download a trial version of Windows 8 and try things out and I am sure if you can get any support in the first place. What I stated in the original version of the entry is that earlier version of the emulators(WP7) do not work inside a vm (tried myself and heard many times). I did not say this in a general term. When I got the WP8 sdk, I tried this and the emulator worked inside a Windows 8 VHD. Hence I entered this article. - The link in the article has very specific steps for setting up a Windows 8 VHD. I cannot do better than that. - If someone can setup a VHD, step2 is just a few clicks away. - The warning you added looks bizarre to me. The initial deployment is always slower if the emulator is not running yet. I have VS2010 and WP7 emulator in Win7. When I deployed a WP7 app (already in the store) in VS2012 to a WP8 emulator in two languages, I did not notice much difference. - I modified the sentence to use BCDEdit or similar programs for adding or removing boot entries. Again this depends on the comfort level of a person in dealing with command lines. - I do not know other way to run a Win8 VHD in a client OS. Other virtualization programs have different file extensions. I am just happy that the WP8 emulator works inside a Win8 VHD.This is just an experiment with n=1. Thanks, Pengguang
17:53, 8 November 2012 (EET)
Pengguang Wu - Comment on Nokia editor's addition of warningAfter coming back from a MS hackathon on Friday, I had to do a system restore due to some networking issues. After the restore, I retested the WP8 emulator. The emulator stayed in the initialization mode waiting for Godot. Closing the emulator caused errors similar to the ones the Admin editor of this site added. I still had the app from the hackathon but lost another one installed after the restore date. Repairing the SDK resolved the issue. If the sdk is damaged the emulator will not run properly regardless of the hardware. Ironic for a company spends so much doing reaching out to developers.
04:47, 11 November 2012 (EET)
Hamishwillee - Thanks for your clarification
I do (and did) understand your points - I was offering some suggestions that would make this more "generally" useful - it is completely your choice not to do so. In line with that I've tidied this up to be more like your original intent.
With respect to the warning, the issue I was trying to convey is that Microsoft say the startup is even slower than you would expect for slower first time boot in this use case. As I don't know why they expect that I've removed that part of the warning (which isn't very helpful anyway). The warning is now accurate and simple.
>If the sdk is damaged the emulator will not run properly regardless of the hardware.
I don't see why this is ironic. The Emulator is part of the SDK - if you break it I wouldn't expect it to work. Perhaps I'm missing something.
Thanks for taking the time to explain this for me. As I said, this certainly is an option for some users.
06:35, 13 November 2012 (EET)