RadMap Bing Maps retirement needs a migration path, not only a warning - #880
Open
dessyordanova wants to merge 1 commit into
Open
RadMap Bing Maps retirement needs a migration path, not only a warning#880dessyordanova wants to merge 1 commit into
dessyordanova wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a WinForms RadMap migration guide intended to help users move off the retiring Bing Maps provider, and reorders the Bing Maps provider documentation navigation to surface the new guidance first.
Changes:
- Added a new “Migrating from Bing Maps” article with capability comparison and before/after snippets.
- Updated the
positionfrontmatter across existing Bing Maps provider articles to accommodate the new migration article in navigation order.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| controls/map/providers/bingmaps/migrating-from-bing-maps.md | New end-to-end migration guide from BingRestMapProvider to AzureMapProvider/custom providers. |
| controls/map/providers/bingmaps/imagery-sets.md | Adjusted navigation position to follow the new migration guide. |
| controls/map/providers/bingmaps/tiles.md | Adjusted navigation position. |
| controls/map/providers/bingmaps/search.md | Adjusted navigation position. |
| controls/map/providers/bingmaps/route.md | Adjusted navigation position. |
| controls/map/providers/bingmaps/truck-route.md | Adjusted navigation position. |
Suppressed comments (1)
controls/map/providers/bingmaps/migrating-from-bing-maps.md:126
- This section claims
AzureMapProviderdoes not implement the RadMap elevation contracts, which conflicts with the AzureMapProvider reference docs that listCalculateElevationAsync. Adjust the narrative/checklist so only the unsupported features (route/truck-route) are treated as mandatory replacements, and elevation is called out as something to validate rather than automatically replace.
`BingRestMapProvider` implements route, truck-route, search, and elevation provider contracts. `AzureMapProvider` implements tile and search functionality, but it does not implement the RadMap route or elevation contracts.
Before removing Bing, identify every call to `CalculateRouteAsync`, truck-route functionality, and `CalculateElevationAsync`. For each call, choose one of the following approaches:
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+1
to
+8
| --- | ||
| title: Migrating from Bing Maps | ||
| description: Migrate a WinForms RadMap application from the retiring Bing Maps provider to Azure Maps or a custom provider, with capability and caching guidance. | ||
| page_title: Migrating from Bing Maps - WinForms Map Control | ||
| slug: winforms/map/providers/migrating-from-bing-maps | ||
| tags: map, providers, bing maps, azure maps, migration | ||
| published: True | ||
| position: 1 |
Contributor
Author
There was a problem hiding this comment.
Yes, the article is intentionally placed inside the Bing provider folder.
Comment on lines
+37
to
+40
| | Routes | `CalculateRouteAsync` | No route contract is implemented by `AzureMapProvider` | Keep routing in an application service, use a provider that exposes routing, or implement a custom RadMap route/provider integration. | | ||
| | Truck routes | `IMapTruckRouteProvider` support in Bing | No corresponding Azure implementation is exposed by `AzureMapProvider` | Plan a separate replacement service or custom integration. | | ||
| | Elevation | `CalculateElevationAsync` | No elevation contract is implemented by `AzureMapProvider` | Plan a separate replacement service or custom integration. | | ||
| | Tile authentication | `BingKey` and optional Bing session initialization | `AzureAPIKey` added to Azure Maps tile and search requests | Create and protect an Azure Maps subscription key. Do not commit a production key to source control. | |
Contributor
Author
There was a problem hiding this comment.
Indeed, the CalculateElevationAsync method is documented in the live docs article. However, the source code doesn't indicate that the AzureMapProvider contains such a method. Please review the documented properties, methods, and events and ensure that they really exist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RadMap Bing Maps retirement needs a migration path, not only a warning
Priority: High
Confidence: 10
Missing Functionality:
The source contains Bing Maps, Azure Maps, OpenStreetMap, local, cache, and provider collections. Bing Maps is being retired while Azure Maps is the current alternative.
Evidence Found in Code:
RadMap/Providers/BingMaps/RadMap/Providers/AzureMaps/RadMap/Providers/MapProviderCollection.csRadMap/Telerik.WinControls.NetCore.RadMap.csprojCurrent Documentation Status:
Incomplete and time-sensitive.
controls/map/overview.mdandcontrols/map/providers/bingmaps/bingrestmapprovider.mdwarn about the Bing retirement, andcontrols/map/providers/azure-map/azuremapprovider.mdshows a basic key setup, but there is no end-to-end migration guide mapping common Bing imagery/search/route scenarios to Azure or custom providers.Remediation Action:
controls/map/providers/migrating-from-bing-maps.mdRecommended Documentation:
Provide a before/after code sample and a capability matrix for imagery, search, routes, elevation, tiles, authentication, and caching.
Business/User Impact:
Existing map applications can lose imagery or service calls after provider retirement. A migration guide reduces outage risk and helps users make informed provider and licensing choices.