The benefits of using Bing Map API and Telerik controls for WPF
August 21st, 2016 11:44 pm Category: Profit Vehicle Planner, by: Steve Cutler
In December of 2014 Microsoft officially discontinued their popular mapping and routing software Microsoft MapPoint. With a number of internally developed products that make use of MapPoint it quickly became obvious that the time had come to modernize these applications to make use of more modern cloud-based technologies. After assessing the different options available to us we came to settle on using Bing Maps as a replacement of the now defunct Microsoft Map Point.
Out of the box, the Bing Map API provides developers with AJAX controls that can easily be embedded in a website. And with the addition of the Bing Maps Representational State Transfer (REST) API, developers can easily add address geocoding, calculate routes (including turn by turn directions) from multiple points and even factor in current traffic levels to the calculated drive time. And to make things even better, Bing Maps is all cloud based so our users no longer have to worry about how current their maps are.
Bing’s Mapping API brings a lot of different features to the table and Telerik adds substantially to the offering all while cutting down on the amount of code a developer has to write to get things going. And since the Telerik controls were already included in the project this also saved us from adding yet another dependency to the mix.
All-in-all this solution provided huge benefits to us in terms of reduced footprint, the ability to customize controls and map behavior, reduce the amount of code required to do common tasks like geocoding an address or plotting a route on the map. And best of all our applications now enjoy a certain measure of being “future-proof”.