Bing Maps: Map Control and Web services Development pemberitahuan
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 Connect pemberitahuan
Live SDK v5.4 is now available for download. New additions to this version of the SDK include:
Windows Store HTML and XAML applications. Version 5.4 of the Live
SDK was updated for compatibility with Windows 8.1 Preview and Visual Studio
2013 Preview, including new behavior specific to Windows 8.1 Preview: For a
LiveAuthClient.LoginAsync will trigger the process to connect the user with a
Microsoft account. Also specific to 8.1 Preview, for users who are not
connected with a Microsoft account, calling methods on LiveConnectClient to
access user data will result in a reject response.
Windows Phone 8. This update contains several fixes for the new
WP8 SDK, including a fix for a login session cache issue that could prevent a
user from logging in with a different account after logging out. Additionally
resolved in this update is a caching issue in LiveConnectClient.UploadAsync
that could lead to additional app memory consumption and less accurate progress
event data when uploading large files. As a result, larger files can be
uploaded on lower-memory devices than was possible in the past.
.NET client and ASP.NET apps. The Live SDK v5.4 Nuget package has
been updated with support for .NET 4.
- Live SDK for iOS apps. Several UI issues related to login in the iOS 6 SDK have been resolved.
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
- The v4.1 API provides the ability to publish activities using activity streams to a user’s Messenger Social feed. We received significant feedback from developers and end users that this functionality is not complete because it doesn’t set the Messenger status field and is thus not visible in the user contact list nor in mobile or previous versions of the Messenger client. In addition, we’ve gotten complaints about the complexity of the data formats required to publish status updates. For this reason, we have updated the activity object available in v5.0 to address these shortcomings. For this reason we are not supporting any new applications using the v4.1 activity publishing APIs although this will continue to function in existing applications. Any new applications that try to use this functionality from the v4.1 APIs will receive a 1073 error.
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:
The final version of the Live SDK v5.2 for Windows 8 and Windows Phone is now available for download here. There are several versions of the Live SDK, depending on your target development platform:
- Live SDK for Windows and Windows Phone: use this edition if you're developing apps for Windows 8 or apps for Windows Phone 7.0 or 7.5. .
- Live SDK for Android: use this edition if you're developing apps for Google Android mobile technology platform devices, like those running Froyo, Gingerbread, Honeycomb, and Ice Cream Sandwich. .
- Live SDK for iOS: use this edition if you're developing apps for the iOS operating system for Apple devices, like iPad, iTouch, and iPod. .
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:
- For Windows desktop apps, and for mobile apps for other than Windows Phone, Android, and iOS, .
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:
- authorization: https://login.live.com/oauth20_authorize.srf
- token: https://login.live.com/oauth20_token.srf
- desktop: https://login.live.com/oauth20_desktop.srf
The old end points are:
Live SDK v5.3 is now available for download here. New additions to this version of the SDK include:
- New .NET SDKs for client and server. Since we first introduced the Live SDK, we have seen a lot of developers ask for a .NET library that would work for classic desktop apps and ASP.NET applications. With this release you can now create applications that target traditional desktop scenarios and as well as server side scenarios. With the client .NET SDK, you can create WPF, Windows Form or console applications that let your users use their SkyDrive data. With the ASP.NET SDK, you can create websites and web server components that talk to the Live Connect API service. Using the SDK also makes it easy for you to incorporate Microsoft account into your identity system or even just use Microsoft account as your primary identity system. Be sure to check out our Build talk “Powering your apps with Microsoft accounts” below to learn more about it.
- Windows Phone 8 SDK. The WP 8 SDK takes advantage of some of the new features that Windows Phone 8 has to offer and provided you with an easy to use programming model by supporting the new Task<T> async pattern and dynamic keyword. With this you can easily move your code between your Windows 8 and Windows Phone 8 application.
- Open source projects for Windows and Windows Phone SDKs. Starting from v5.3, all Live SDK client components written in C#, Objective C and Java are released as open source projects. This makes it much easier for developers to resolve problems quickly and build solutions that are tailored to their scenarios. Be sure to check out our gibhub depot for new additions of the Windows and Windows Phone SDK source code.
- New samples and starter guides. New samples for Windows and Windows Phone are added as part of the open source Windows SDK projects. We also have an updated starter guide for Windows Phone 8 and a new one for Windows 8 and Asp.Net.
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.
Windows Live Writer: Development pemberitahuan
Click on this link to get technicle support for windows live writer
Also visit The Writers Zone for the latest updates
Have ideas for future requests? Or, want to give feedback. The live writers team would love to hear your ideas.
Windows Live Messenger Client: Development (retired) pemberitahuan
This link provides more information, and provides tools to remove the msn virus
For Microsoft Exchange questions, please post in this forum listed below
Windows Live Messenger Web APIs: Development pemberitahuan
We are happy to announce that Windows Live Messenger Web Toolkit V3.7 has been released.
See our blog posting for more information.
Thanks for supporting the Messenger Web Toolkit!
Windows Live Spaces: Development pemberitahuan
Please click on the link for more information and removal tools
If you want to make a suggestion for a new space feature in the future, please click on the feedback button at the bottom of your space. Or you can offer feedback, stay up-to-date with spaces plans, or make suggestions for new features at the live space team blog at the link below
For API and Live developer app issues , please direct your questions and feedback to the Developers Lounge area in the Bing Community forums