none
Bing Maps V7 control and SOAP Web Services deprecation on June 30 RRS feed

  • Question

  • Hello!

    I have received an email to understand that the v7 control and soap web services are going to be deprecated. The question is, we have a mapping solution built using the v7 REST full services (https://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=7.0), should we migrate our code from 7.0 to 8.0?

    Thanks for clarifying!

    Chaitanya...

    Friday, June 2, 2017 1:46 PM

Answers

  • At a minimum you will want to test your app against V8 so you know what will break when the map script is redirected to the V8 script at some point. On July first a few V7 features are expected to be disabled, birdseye and the search module (uses the SOAP services). V8 has a new birdseye experience and the search module in V8 uses the REST services.

    The type most common breaking changes between v7 and V8:

    - HTML pushpins are not natively supported as V8 uses an HTML5 canvas for rendering. This provides the ability to render a lot more data than in previous controls, but doesn't allow for rendering of DOM elements. However, if you need HTML based pushpins, there is a code sample on how to achieve this using a custom overlay here: http://bingmapsv8samples.azurewebsites.net/#Html%20Pushpin%20Layer

    - Adding Infoboxes. In V7 you added infoboxes to the map the same way you did any other shape, which ended up causing issues (pushpins appearing about infoboxes). At the end of the day, an infobox isn't a shape and shouldn't be added to the map in the same way. In V8 you instead assign a map to the infobox to add it. For example: infobox.setMap(map)

    A migration guide can be found here: https://social.technet.microsoft.com/wiki/contents/articles/34563.bing-maps-v7-to-v8-migration-guide.aspx

    Note that I believe this is the 4th or 5th email sent out about the end of life of V7 and SOAP services in the past year.


    [Blog] [twitter] [LinkedIn]

    Friday, June 2, 2017 9:51 PM

All replies

  • At a minimum you will want to test your app against V8 so you know what will break when the map script is redirected to the V8 script at some point. On July first a few V7 features are expected to be disabled, birdseye and the search module (uses the SOAP services). V8 has a new birdseye experience and the search module in V8 uses the REST services.

    The type most common breaking changes between v7 and V8:

    - HTML pushpins are not natively supported as V8 uses an HTML5 canvas for rendering. This provides the ability to render a lot more data than in previous controls, but doesn't allow for rendering of DOM elements. However, if you need HTML based pushpins, there is a code sample on how to achieve this using a custom overlay here: http://bingmapsv8samples.azurewebsites.net/#Html%20Pushpin%20Layer

    - Adding Infoboxes. In V7 you added infoboxes to the map the same way you did any other shape, which ended up causing issues (pushpins appearing about infoboxes). At the end of the day, an infobox isn't a shape and shouldn't be added to the map in the same way. In V8 you instead assign a map to the infobox to add it. For example: infobox.setMap(map)

    A migration guide can be found here: https://social.technet.microsoft.com/wiki/contents/articles/34563.bing-maps-v7-to-v8-migration-guide.aspx

    Note that I believe this is the 4th or 5th email sent out about the end of life of V7 and SOAP services in the past year.


    [Blog] [twitter] [LinkedIn]

    Friday, June 2, 2017 9:51 PM
  • Thank you so much for the response. This helps a lot!

    Saturday, June 10, 2017 12:39 AM