none
Is the latest Bing Maps SDK supported on ARM? RRS feed

  • Question

  • I am attempting to use the Bing Maps SDK for Windows Store apps in a XAML/C# project. The SDK I am using was last updated 10/30/2012 (1.1.20120927.1) and the docs here (http://msdn.microsoft.com/en-us/library/hh855146.aspx) suggest that ARM is supported, however I get a XAML parse exception when I execute a debug build remotely on a Surface RT. If I change the target to x64 the code runs fine in the simulator.

    Is there any way to get this scenario to work right now?


    Daren

    Monday, November 5, 2012 10:01 PM

Answers

  • Quick Update: I was able to finally get this to run but I had to switch to the Release build. Also, make sure you have a reference not just to Bing Maps but also to the Visual C++ Runtime package.

    I'm not sure exactly why the Debug build won't run but my current theory is that it's related to VS not being installed on the remote machine and hence it's missing something expected...

    • Marked as answer by DarenMMVP Tuesday, November 6, 2012 3:26 PM
    Tuesday, November 6, 2012 2:12 PM

All replies

  • Yes this works on Arm.

    Beware changing to remote debug also changes the build target often, so make sure both "remote debugging" and ARM has been selected.


    /Morten
    twitter: http://www.twitter.com/dotMorten
    blog: http://www.sharpgis.net

    Tuesday, November 6, 2012 6:05 AM
  • I'm getting the same errors when trying to test on a Surface. I don't think it's a build target issue - if that gets changed you'll get a deployment error. The funny thing is that I get the same errors trying to run the samples remotely as well. Makes me thing somethings not right with the SDK . . .
    Tuesday, November 6, 2012 1:53 PM
  • Quick Update: I was able to finally get this to run but I had to switch to the Release build. Also, make sure you have a reference not just to Bing Maps but also to the Visual C++ Runtime package.

    I'm not sure exactly why the Debug build won't run but my current theory is that it's related to VS not being installed on the remote machine and hence it's missing something expected...

    • Marked as answer by DarenMMVP Tuesday, November 6, 2012 3:26 PM
    Tuesday, November 6, 2012 2:12 PM
  • These "issues" with the SDKs is getting to be really frustrating. I now have two SDKs in my solution that require me to be constantly switching between target CPU platform and now build configuration so I can design with Blend and then compile and run - the smooth streaming SDK and the Bing maps SDK. Now, with the Bing SDK I can't even debug easily if I hit timing/resource issues on the Surface.

    This is a very poor experience!


    Daren

    Tuesday, November 6, 2012 3:31 PM
  • These "issues" with the SDKs is getting to be really frustrating. I now have two SDKs in my solution that require me to be constantly switching between target CPU platform and now build configuration so I can design with Blend and then compile and run - the smooth streaming SDK and the Bing maps SDK. Now, with the Bing SDK I can't even debug easily if I hit timing/resource issues on the Surface.

    This is a very poor experience!


    Daren

    I also had an extremely poor experience with this, my app submission fail due to I included the ARM distribution, if I remove the ARM distribution with the same build, it pass the certification. But the build was able to deploy to WinRT!

    anybody have the experience that how to make the Windows Store App for WinRT with Bing Maps SDK pass the certification? maybe can share the tricks and tips!

     

    Snake Chia http://www.nearby.com.my

    Friday, November 9, 2012 9:49 AM
  • Daren

    I also had an extremely poor experience with this, my app submission fail due to I included the ARM distribution, if I remove the ARM distribution with the same build, it pass the certification. But the build was able to deploy to WinRT!

    anybody have the experience that how to make the Windows Store App for WinRT with Bing Maps SDK pass the certification? maybe can share the tricks and tips!

     

    Snake Chia http://www.nearby.com.my

    My first store submission passed Cert with all 3 builds (ARM, x64, x86) however we needed to patch it with some minor bug fixes completely unrelated to Bing Maps and now we failed due to "WACK test does not pass on Windows RT".  However I was able to procure a Surface RT device and immediately ran the WACK test on the same build and it passed.

    That said, I also ran some remote debugging on Surface RT in Debug configuration and received the XamlParseException() exception.  This was resolved by changing the Remote debugging to use Release configuration and all was good.  I can't make sense of whether this exception is the reason it failed the Store Cert considering we only posted a RELEASE build to the store obviously.

    I'm a tad annoyed that our first build passed without a hitch and a minor bug fix caused a re-submit after the initial approval and now we get rejected.  The information coming with the Rejection simply states that we didn't pass WACK on Windows RT but I was able to download the WACK tool on Surface RT and my first attempt against the build we submitted PASSED.  Go figure.


    • Edited by CombYoBeard Wednesday, November 14, 2012 2:27 AM
    Wednesday, November 14, 2012 2:25 AM
  • I don't have the Surface as like you, which I wish to have it. too bad, the country that I stay wasn't selling it.

    But, I did manage to loaded my app to the Asus Vivo, which is an ARM version of the WinRT, all ran without problems. This is getting frustrated as the emulator can't simulate the ARM version.


    Snake Chia http://www.nearby.com.my

    Sunday, November 18, 2012 7:55 AM