This is a place devoted to giving you deeper insight into the news, trends, people and technology behind Bing.
Back in August, I announced the Beta for our Bing Maps WPF control. The uptake in the Microsoft Developer Community has been stellar and the feedback – immensely helpful. As a result and as promised to those across the Microsoft Developer Network, we’re officially releasing The Bing Maps Windows Presentation Foundation Control, Version 1.
The control was built atop of the beta, so we still have all of the touch enabled greatness for Surface v 2’s Pixel Sense, inertia and full rotation. We’ve kept most of the classes, methods and properties in place from the beta – requiring little work to install and register v1. And, per community feedback on the Bing Maps MSDN Forums we added the following features (and fixed a few bugs):
I have to give it up for my (small) crack team of people involved in the making of the WPF Control. This was one of those 10% projects that we all really had a passion to get done because it was the right thing to do for the Microsoft Developer Community. So, we found the time, slipped the release a month (for quality) and, as the guys over in Surface said, “just got it done.” Our internal motto kept stoking the fire to push this bad boy out the door…”WPF, FTW!”
Now, download the Bing Maps WPF Control, build a killer app and make us proud.
CP
Thank you very much!
I searched the CHM for info about SSL Support, but can't find any. Any documentation / blog about this?
Map.usehttps
msdn.microsoft.com/.../microsoft.maps.mapcontrol.wpf.map.usehttps.aspx
Great news! Congratulations.
Now on to the WinRT version... :)
social.msdn.microsoft.com/.../1e56718c-50f2-4847-bdd9-db81030b295b
go.microsoft.com
Brilliant!
I have noticed a problem in case of transparent tiles in a MapTileLayer. Here you see a screenshot:
social.msdn.microsoft.com/.../af2bb23b-d49a-439f-a156-430193b7636b
Is there someone that knows a workaround?
Anyway, I am unable to use the control, because of the online requirement and the mandatory Bing Maps key verification. Why should there be a key verification if I don't use Bing Maps?
I always give my customers the choice whether they want to pay for Bing Maps tiles or not. I am not able to give them the choice of a satellite view with this control now. A pity ... and a big loss of customers.
Map seems to fail credentials validation if the Map object is in a custom control.
Hardcoding the dev-key doesn't work, and I have found no other way to relay credentials from a caller.
Server:BLUBINGCOMWS3