To enable developers to test applications that somehow rely on location services without having an actual device, Microsoft added a location tool to the Windows Phone emulator back in Mango release. For some reason, the tool stopped working and the Bing map is not rendered if you try to use it today. Without a map, you can’t add pushpins to it which would simulate your device actually having latitude and longitude – location somewhere on Earth. Luckily, there’s a workaround!
EDIT: The problem has been recognized by Microsoft, and the team seams to be working on it. Currently, there is another workaround shared by Eric Fleck from Microsoft here: http://forums.create.msdn.com/forums/p/107391/633268.aspx
It comes down to change registry entries. Seriously, have in mind that you are doing this at your OWN RISK!!
To work around the problem by adding a Browser Emulation mode entry for XDETools.exe in the registry.
caution: The side-effects of this work-around are unknown. (… I have only done ad-hoc tests to verify it works.)On 64 bit Windows use:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInternet ExplorerMAINFeatureControlFEATURE_BROWSER_EMULATION]
“XDETools.exe”=dword:00002328on 32 bit Windows use:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMAINFeatureControlFEATURE_BROWSER_EMULATION]
“XDETools.exe”=dword:00002328
Thanks to my reader danipham for sharing this down in the comments.
Keep reading if you’d like to know how to edit the location entries yourself without the map. :)
First I thought that I was the only one having this problem. Then I noticed a question on StackOverflow which described the problem I was having, so I assume that something is actually wrong with the Bing service that was responsible for the map in this tool.
What if the map doesn’t show, and you need the emulator location tool immediately? When the map doesn’t show, it displays a blank, white screen, like this:
If you have recorded some data earlier when the location tool was working, then you can simply load it by pressing the Load button in the lower right corner of the tool. But what if you haven’t?
The location data is recorded in XML file format. It has a very simple structure. Simply open Notepad or any other plain text editor and add your locations in the following structure:
<?xml version="1.0" encoding="utf-8"?>
<WindowsPhoneEmulator xmlns="http://schemas.microsoft.com/WindowsPhoneEmulator/2009/08/SensorData">
<SensorData>
<Header version="1" />
<GpsData latitude="" longitude="" />
<GpsData latitude="" longitude="" />
<GpsData latitude="" longitude="" />
</SensorData>
</WindowsPhoneEmulator>
[/sourcecode]
I found this answer thanks to “Konaju Games” on AppHub forum and decided to share it here for everyone who might encounter the same situation.
The main tag is WindowsPhoneEmulator, and it has a child element SensorData. SensorData has GpsData children which represent different locations on the map. They are defined by latitude and longitude. I suggest you use Bing maps to get the latitude and longitude of particular locations. Go to
Then find the location you need and right click on it. A popup will open with two double values on the top which are latitude and longitude, respectively.
Enjoy, test your app using the emulator location tool if you don’t have a device, and get the app published as soon as you can. ;)
Thanks I’ve been trying to fix this for almost a day now! I actually just reinstalled the 7.1 SDK. I assume we just keep trying to use it and when fixed it will work?
Completely different question but I’d like to be able to “simulate/test” the geowatcher accuracy (e.g 3000m vs 400 s 6m) as it hones in on your location. It seems that whenever you ask for location data, it is already honed in. I’d almost like to be able to “change” this value to simulate signal strength changes etc.. This can be very important in testing a location aware app.
See the workaround from Eric Fleck – Microsoft at
http://forums.create.msdn.com/forums/p/107391/633268.aspx
On 64bits Windows:
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInternet ExplorerMAINFeatureControlFEATURE_BROWSER_EMULATION]
“XDETools.exe”=dword:00002328
On 32bits Windows:
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMAINFeatureControlFEATURE_BROWSER_EMULATION]
“XDETools.exe”=dword:00002328
Thanks! I added it to the post, of course mentioning that you let me know about it. :)
BIG thank you!
So far, I have opted to to wait it out for the fix rather than make risky registry changes etc… Does anyone know if they are still working on this or if this issue has been resolved?
If fixed, how to we implement.
If still in progress, do we just keep trying to access the live location untill it starts working again?
The fix doesn’t work for me. I have 64-bit version of Windows 7 Professional. Does anyone have some information regarding this problem? Forum link provided doesn’t work as well – it seems that Microsoft made some changes to their WP7 site.
I waited it out and finally added the registry entry. After I did so, it is working for me again. What disappoints me more is when there is absolutely no communication telling you if they are working on the issue or not.
I believe they are working on the issue…
Try searching the official forums, they might be telling you more…
Sorry guys – fix is working. I’ve tried to change registry entry manually instead of creating .reg file, and it’s working now. If you have 64-bit operating system, I suggest you to do the same. Also, if it doesn’t work, try creating hex key in [HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMAINFeatureControlFEATURE_BROWSER_EMULATION], i.e. without ‘Wow6432Node’ in registry path.