In using the .NET Runtime in WPF, we've noticed something odd with max extent. If a TPK is the first basemap loaded to the map, it can set the MapView's maximum extent, restricting pan/zoom to only the extent of the TPK. This is an issue because we allow them to specify any number of basemaps and freely switch between them. As one can guess, it is frustrating to switch to an imagery layer and not be able to pan to anywhere you'd like to.
We could get around this problem by always loading a world-wide basemap first. However, we want users to have a fully useable app when starting it while offline. Since the MapView breaks if it can't get to the first basemap added, this isn't a viable option.
Is there a way to programmatically remove/prevent the pan/zoom limits?
We have the same issue where we aren't using a worldwide map, but small detailed maps for areas of interest, and unfortunately it sets the extent and min/max scale to the first layer as described here. We plan to workaround this by adding a blank worldwide map, but this is not ideal, as we would like it to restrict the zoom to the combined extent of the loaded basemaps.