Hi Anil,
Thanks for your questions. For the first issue, it is a license limit with the Bing Maps Imagery service. Every requested tiles returns an image with a logo. Technically, it’s possible to get rid of it. But we are not sure if it’s legal or not. Hope you understand. We will check this out and see if we can leave only one logo on the entire screen.
For the second question. I think you have noticed that the BingMapsTileOverlay is much faster than the BingMapsLayer right? We made a lot of enhancement on this but the speed still cannot catch up with the web edition. Because they are requesting totally different imagery service. For web edition, we directly wrap BingMaps Ajax library to our product, every tile request directly to its server. While for Wpf, the requested service is totally different. For example, to request an image, we need access the service twice. First step, we need to access a web service to request a available uri; then request the real image by the requested uri. Hope you understand they are using totally different license strategies. We can also use this service which is faster as you think in WPF, but you know, we are still limited by there license strategy.
On the other hand, another reason is that, compare to the web edition, we still need to consider the limit of the request balance to the server which means we cannot send too many requests at a time to avoid the HTTP500 etc exception from the server.
Hope you understand and feel free to let us know if you have more queries.
Thanks,
Howard