Changes

To see the fixes and features included in our latest official release please refer to our Release History .

R2 2017

BingMapProvider, BingRouteProvider, BingSearchProvider, BingGeocodeProvider are deleted.

The providers use the old Bing SOAP services which will be stopped in June 2017. Instead, you can use the new REST map provider.

The BingMapProvider can be easility replaced with BingRestMapProvider using the same Bing Key. BingRestMapProvider is REST services based and displays the same image map tiles the BingMapProvider does.

BingRouteProvider and BingGeocodeProvider can be replaced with BingRestMapProvider.

BingSearchProvider has no replacement currently in RadMap. This is because Bing stops the SOAP Search API in June 30 2017 and they also have no current replacement for search. They might release a new REST based search API as stated in this forum post.
BingMapTrafficProvider is deleted.

This is due to a limitation in the Bing Maps developer API terms of use. Also the service which stays behind this provider might be stopped at some point, so if you use RadMap with old version (before R2 2017), this provider might also stop working.

Currently there is no direct replacement of BingMapTrafficProvider. Instead, you can use Bing REST Traffic API and retrieve traffic information. Then you can use the data and display map objects over RadMap. You can check the Using the REST Services with .NET MSDN tutorial.

Fixed: The AsyncShapeFileReader does not read very small DBF-files
Fixed: BingMapProvider memory leaks
Fixed: InvalidOperationException is thrown when using VisualizationLayer and changing themes runtime
Fixed: Specific PathData is not displayed in VisualizationLayer

Feature: Add ability to setup RectangleGeometryData using coordinates of the top-left (NW) and bottom-right (SE) corners of the rectangle