none
New Bing Maps V8 control announced RRS feed

  • General discussion

  • Today the Bing Maps team announced the release of a new HTML5 powered map control. It is fast, feature rich and developer friendly. Several new and exciting features such as Autosuggest, Streetside imagery and many business intelligence tools.

    See the official announcement here

    BingMapsISDK


    http://rbrundritt.wordpress.com

    Tuesday, April 5, 2016 6:41 PM

All replies

  • Great to see a new version.

    (Funny, just filled in a Bing maps survey. A Roadmap for the future was one suggestion, as not much had changed recently. Well, the not-much-changed has been fixed!)

    An article on what's new, what's changed, and what's removed would be nice. (e.g. why are some classes prefixed by "I"?).

    The documentation does have a "removed" section.

    A few examples in the documentation would be very helpful, e.g adding layers.

    Andrew

     

     
    Tuesday, April 5, 2016 7:45 PM
  • We showed off the V8 SDK last week at build and talked about the roadmap as well. We are trying to be a more open in that regards as we have been doing a lot of innovative stuff but some teams get nervous sharing things before they are set in stone (i.e. about to be released).

    We do plan on writing a series of blog posts on V8 around the new features. I will also be putting together a migration document for those on V6.3 and V7. This will include information on what has been removed. We have started an initial list here: https://msdn.microsoft.com/en-us/library/mt712870.aspx It isn't complete as V8 has been released as a preview, so some things that are missing are still in development, where as this list is of things that are not planned to be included. There may be some additions to this list as we go on

    The classes that start with an "I" are interfaces and actually don't have a strongly typed class. These generally consist of options or response objects. These are basic JSON objects. You can't create instances of these. For example, this wouldn't work;

    var options = new Microsoft.Maps.IPushpinOptions(); 

    As there is no such class. Instead you would do something like this:

    var options = { icon: 'URL to image' };

    V7 worked the same way, but we didn't mark these classes as interfaces in the documentation and it caused confusion with developers who tried to create instances of these non-existent classes.

    There are a bunch of code samples under the Map Controls section of the documentation: https://msdn.microsoft.com/en-us/library/mt712558.aspx

    We also crated a brand new interactive SDK for V* that is filed with code samples that can be edited and run right in the browser. General feedback from V7 developers has been that the interactive SDK we created for it was much more useful and easier to go through than the MSDN documentation. We plan to add a bunch of descriptions/documentation in the interactive SDK with the samples as well so you don't have to flip back and forth. You can check it out here: http://www.bing.com/api/maps/mapcontrol/isdk 


    http://rbrundritt.wordpress.com


    Tuesday, April 5, 2016 8:14 PM
  • Ricky,

    Thanks for the information.

    Testing the autosuggest feature, I noticed that the suggestionResult returned object contains a property « PostalCode » but that it has no value sent back to us (undefined)

    Is returning the proper postal code something you plan to implement or is it already implemented but just not available for french adresses or the particular adress I used in my tests ?

    Thanks for your time

    Christophe

    Wednesday, April 6, 2016 11:53 AM