none
Bing maps migration to V8 in Silverlight App RRS feed

  • Question

  • Hi Team,

    We have a Silverlight application with Bing map control which is perfectly
    working now. We have noticed that V8 version has been introduced recently. As per the
    announcement the current sliverlight bing map control will not work after November 30.

    We seeking help from you, can you please suggest what would be the best approach to
    set out application to work normally even you release V8.

    Please suggest us to migrate or any alternative.

    Thanks,

    Anil Pandilla


    Friday, October 7, 2016 2:50 PM

Answers

  • Hi Anil,

    You have a few options.

    If you plan on continuing to use Silverlight in your application for a long time, you can add Bing Maps in the JavaScript page in which your Silverlight control is hosted and float the map over top of your Silverlight display. http://stackoverflow.com/questions/782415/displaying-html-divs-over-Silverlight This approach would require writing a communication layer between your Silverlight and JavaScript code. Note overly difficult to do, but can take some time to do and may be a pain for debugging. I've done something like this ages ago for an application that wanted to display HTML adds over a section of the Silverlight app.

    If you plan on using Silverlight for next while but eventually plan to migrate to HTML5. You can try and continue to use the Silverlight control. When the Bing Maps Silverlight control reaches end of life, initially, nothing will happen and it will continue to work. Eventually some of the underlying services that power the control will be turned off. The primary service being the base map tiles. This will happen without warning after the control is retired. However, you can extend the life of the control by loading in the Bing Maps tiles directly. Here is a code sample: https://1drv.ms/u/s!AgFqp4QkIjUNnaloIU8mRJ1HLQ2amw There is no guarantee that this work around will work forever, but it should keep the Silverlight control running beyond the end of life date for a while. That said, this same approach is used by a number of non-Microsoft map controls which have a Bing Maps option (leaflet, openlayers, cesiumjs, ArcGIS...)

    The third option is to migrate your app over completely to HTML5. If your app is a public facing app, then this likely is something that should be done sooner rather than later as Silverlight is blocked in many new browsers. If your app is used internally and you have control over the browsers that your users have access to, then I can understand the lack of rush to get off of Silverlight.


    [Blog] [twitter] [LinkedIn]


    Monday, October 10, 2016 9:45 PM
  • At present the tile URL's will be the same. The imagery metadata service will be updated to point to the dynamic tiles before the static tiles are removed.

    The client access policy doesn't matter and not related to the workaround.


    [Blog] [twitter] [LinkedIn]

    Thursday, October 27, 2016 6:46 PM

All replies

  • Hi Anil,

    You have a few options.

    If you plan on continuing to use Silverlight in your application for a long time, you can add Bing Maps in the JavaScript page in which your Silverlight control is hosted and float the map over top of your Silverlight display. http://stackoverflow.com/questions/782415/displaying-html-divs-over-Silverlight This approach would require writing a communication layer between your Silverlight and JavaScript code. Note overly difficult to do, but can take some time to do and may be a pain for debugging. I've done something like this ages ago for an application that wanted to display HTML adds over a section of the Silverlight app.

    If you plan on using Silverlight for next while but eventually plan to migrate to HTML5. You can try and continue to use the Silverlight control. When the Bing Maps Silverlight control reaches end of life, initially, nothing will happen and it will continue to work. Eventually some of the underlying services that power the control will be turned off. The primary service being the base map tiles. This will happen without warning after the control is retired. However, you can extend the life of the control by loading in the Bing Maps tiles directly. Here is a code sample: https://1drv.ms/u/s!AgFqp4QkIjUNnaloIU8mRJ1HLQ2amw There is no guarantee that this work around will work forever, but it should keep the Silverlight control running beyond the end of life date for a while. That said, this same approach is used by a number of non-Microsoft map controls which have a Bing Maps option (leaflet, openlayers, cesiumjs, ArcGIS...)

    The third option is to migrate your app over completely to HTML5. If your app is a public facing app, then this likely is something that should be done sooner rather than later as Silverlight is blocked in many new browsers. If your app is used internally and you have control over the browsers that your users have access to, then I can understand the lack of rush to get off of Silverlight.


    [Blog] [twitter] [LinkedIn]


    Monday, October 10, 2016 9:45 PM
  • Hi Ricky,

    Thanks for your information and support.

    We have implemented the Dynamic tiles in our Silverlight Application. The Tiles Navigation is getting overridden, we can see the Http and Https Get requests and results are getting cached on first request.

    http://dev.virtualearth.net/clientaccesspolicy.xml

    https://dev.virtualearth.net/clientaccesspolicy.xml

    http://ecn.t0.tiles.virtualearth.net/clientaccesspolicy.xml

    Without Dynamic Tiles implementation, the Http Get request can be seen below.

    http://dev.virtualearth.net/clientaccesspolicy.xml

    http://ecn.t0.tiles.virtualearth.net/clientaccesspolicy.xml

    It seems like we are using same Url's for both.

    Please let me know, how to make sure that Dynamic Tiles is working.

    Thanks,

    Anil Pandilla


    Thursday, October 27, 2016 8:58 AM
  • At present the tile URL's will be the same. The imagery metadata service will be updated to point to the dynamic tiles before the static tiles are removed.

    The client access policy doesn't matter and not related to the workaround.


    [Blog] [twitter] [LinkedIn]

    Thursday, October 27, 2016 6:46 PM