Today we announced the new Bing Maps developer forums. Rather than having a single forum for Bing Maps we have created 5 seperate froums grouping liked API's. In addition we have also created a Bing Maps category in the MSDN forums which you can access here: http://social.msdn.microsoft.com/Forums/en-US/category/bingmaps
The original announcement can be found here: http://www.bing.com/community/site_blogs/b/maps/archive/2012/03/16/the-bing-maps-forums.aspx
Since its release earlier this year, we have seen interest in, and usage of, our Bing Maps Spatial Data Services (SDS) grow rapidly.
The result is that at times of peak load the number of evaluation accounts using the service is pre-empting other requests. Today we have made a change to the SDS service that will prioritize requests from Enterprise Accounts. You can check the status of your Account to see if you have an Enterprise Account by logging into the account on the Bing Maps Account Center.
We regret that this means that you will no longer be able to submit new jobs to SDS from non-Enterprise Accounts until you request and are given access to SDS as detailed below. To be clear, data already uploaded to the SDS service can still be queried; it is only when you try to update those data sets, create new ones, or download them that you will receive an error.
If you would like to request access to SDS for a non-Enterprise Account application, you can do so by emailing MAPLIC@microsoft.com with your Account ID and (for publically accessible sites) top level domains. Be sure to send this request from the email account on record in the Bing Maps Account Center. (Replies will only be sent to these accounts so please check your SPAM filters and the usual things that might complicate communication.)
Please also note that if you are using the SDS service from an Enterprise Account, then you should not need to take any action related to production accounts. Your application should not require any changes. If you experience any issues please let us know via your enterprise support contact.
As we continue to enhance the SDS system this process will be improved and made more efficient. We apologize for any inconvenience this may cause.
Sr. Program Manager, Lead
Bing Maps, Microsoft Corp.
On the 2nd November 2010, Microsoft announced that they have discontinued investment in the Bing Maps 3D control Active-X plug-in.
When the next update to www.bing.com/maps is launched, the option to view 3D Maps will be removed.
Current users of 3D Maps can expect the following:
1. Permalinks and the desktop shortcut to 3D Maps will be redirected to Bing Maps with the nearest match to the experience they had in 3D. In most cases this will result only in a loss of the ability to navigate in full 3D.
2. After opening collections with 3D models, the 3D models will be represented as pushpins only. The models will not be accessible from collections.
3. Permalinks to tours will now open the collection manager with a message indicating discontinued support of the feature. Unfortunately there will no longer be an option to view the tour.
The 3D API used by developers to implement 3D mode in their own Bing Maps (http://msdn.microsoft.com/en-us/library/bb429547.aspx) will continue to be supported until December 2011.
You can view the announcement by Brian Hendricks, Bing Maps Product Manager, at: http://www.bing.com/community/site_blogs/b/maps/archive/2010/11/02/changes-to-bird-s-eye-and-3d-maps.aspx
Released today, the Bing Maps v7 Interactive SDK demonstrates the code required to perform common tasks on the Bing Maps v7 control - how to add shapes to the map, working with tile layers, adding events to the map, together with new features such as getting the user's location and registering custom modules.
You can access the interactive SDK here: http://www.bingmapsportal.com/ISDK/AjaxV7
If you have any questions about the examples used in the iSDK, please start a new thread onthe forum
Live SDK v5.4 is now available for download. New additions to this version of the SDK include:
When we shipped the Live Connect API service 5.0 April last year, we included the functionality to allow an app to provision applications on behaves of other developers. This functionality is enabled if the app has permission to use the wl.application and the wl.application_create scope. Application information can be access through the https://apis.live.net/v5.0/me/applications path. After observing the usage pattern of this API for more than a year, we have concluded that this API does not fit into the user model and the design goals of the Live Connect API, whose primary objective is to provide developer access to user’s data stored in Windows services, not a platform to auto provision applications. With that, we’re now announcing the plan to decommission any APIs that are related to application provisioning through the Live Connect API service, which include all calls to the https://apis.live.net/v5.0/me/applications path and its sub-paths. These APIs will stop working in March 2013.
With the release of v5.0 of the Messenger Connect API, the previous version is now deprecated. As mentioned in the v5.0 announcement blog post, the latest version of the Messenger Connect API is the result of taking into account a lot of the input from developers about how to simplify the API and address key limitations we had in the previous version.
The v4.1 API will continue to function and will be supported for one year after the release of the v5.0 API. New applications are strongly encouraged to use the v5.0 Messenger Connect instead of the deprecated v4.1 API. It is also recommended that when you upgrade or modify existing applications avoid using and remove usage of the v4.1 APIs.
Below is a list of v4.1 features that will no longer be supported in new applications with the release of v5.0 of the Messenger Connect API
In summary, the v4.1 Messenger Connect APIs are deprecated and ceased working on August 14, 2012.
Last year, we announced that support for Messenger will end in 2013. Apps that already use Extensible Messages and Presence Protocol (XMPP) will continue to be supported until October 2013. We strongly discourage any new implementations relying on XMPP. Instead, we encourage you to learn more about our APIs for SkyDrive, Hotmail and Skype at http://dev.live.com.
The documentation for XMPP and messaging has been removed from the Windows Dev Center and archived. This info will not be updated and might contain links to content that no longer exists. But you can still find the XMPP topics here if you need them:
We’ve also added the following new features in the REST API as highlighted in this SkyDrive blog post.
If you're developing apps for other platforms, you don't need to download the Live SDK; you can reference our updated Representational State Transfer (REST) API directly, as follows:
If you have any questions about these downloads or about the Live SDKs in general, post them in this forum. We have team members here that are ready to help you.
This forum is monitored by Live Connect Support and Product Group team.
Hours of Operation: 8:00AM – 5:00PM US Pacific Time (Monday – Friday)
We do not provide any support over the weekend (Saturday-Sunday).
Live Connect Support Team
We would like to inform you of about the changes to the OAuth 2.0 SDK. We have transitioned the OAuth endpoints to https://login.live.com. This change is to move our OAuth 2.0 authentication service to be on the same backend as our primary login infrastructure. It will give increased scalability and reliability to our OAuth interface and also add some security features like invalidating refresh tokens if the users are detected as compromised or has changed their password.
The https://oauth.live.com endpoints will continue to function but with slightly increased latency so we recommend you begin using the new URL’s.
The new endpoints are:
The old end points are:
Live SDK v5.3 is now available for download here. New additions to this version of the SDK include:
SkyDrive REST API enhancements - we have added the ability to search for files in a user’s SkyDrive by using a partial file name. You can do this by simply making an HTTP GET call with the search parameter 'q'. Here is an example:
The response contains the list of files that have “expenses” in the file name.
For API and Live developer app issues , please direct your questions and feedback to the Developers Lounge area in the Bing Community forums