Programming for Mobiles - Practical 7
Developing for Windows Phone
Starting the Windows Virtual Machine
We'll be using virtual machine images to run Windows 7 and Visual Studio Express 2010 for Windows Phone Development. These are designed to run with VMWare player. If you have your own Windows environment then please feel free to use that instead.
- Start the player by running the command /usr/groups/linux/extra-packages/VMWare/cmds/vmplay from a terminal.
- Accept the license agreement
- If you see a warning about /tmp/vmware.log then you can ignore it
- VMWare Player will ask if the VM has been moved or copied - choose copied
- You can ignore the Hint about system swap space and warnings about graphics support
- You can also ignore the offer to download VMWare Tools for Windows 2000 or later.
- Windows should start. You might need to go through a few screens of setup. If you need to create a user then use username P36WinPhone and no password.
- Don't forget you need to unlock your handset. The program to do this is in the Start menu under Windows Phone SDK
- When you connect your phone you'll get a message from the host operating system (Ubuntu) asking what to do - you should just click cancel on this.
- You will also see a message from VMWare warning you that "The specified device is in use by process:XXX". You should click ok on this to continue.
- Windows should then mount the device and Zune should start. Go through the Zune setup - if an update is available for the device you can just ignore it and choose Update Later
- To access your files from the virtual machine you need to create a shared folder. Do this by choosing "Virtual Machine Settings" from the "Virtual Machine" menu and choose the "Options" tab. Look for "Shared Folder" and set Folder Sharing to be always enabled. Also tick the "Map as a network drive" box. Then you need to add your home directory (or whatever) as a share and click Save. Remember that the VM image is specific to the machine you are working on and is shared amongst all users of that machine so you shouldn't leave personal data or saved passwords etc. inside the VM.