What's New in This Release of Messenger Connect
|Current information about Live Connect is now available in the Windows Live Developer Center. The information in the following sections is provided for legacy purposes only.|
Welcome to Windows Live Messenger Connect. This topic summarizes changes and new features, and provides information that you need to be aware of before you begin to work with this release.
The following sections summarize the changes and improvements in the current release.
.NET Library Discontinued
Based on feedback from early adopters, the strongly typed Messenger Connect .NET library has been discontinued. Future development efforts in this area will focus on samples that work directly with our REST-based web services.
Profile API Enhancements
The Messenger Connect API now has a new data format for user profiles. This format condenses all available profile data into a single class, making it easier to retrieve the data by reducing the number of calls required to access it. For details, see Microsoft.Live.Services.Profile.
The user's thumbnail image link can now be accessed without authentication. This feature can help an application to save time and resources, because it is no longer necessary to authenticate to get the thumbnail image link. For more information, see Microsoft.Live.Services.Profile.thumbnailImageLink.
Invite Friends API
New in version 4.1, the Messenger Connect API provides a way for users to send out email invitations to their Windows Live friends. For example, a user could invite friends to go see a movie or could participate in an online gaming session. For details, see Working with Invitations.
Chat Control Moderation
Messenger Connect now provides the ability to moderate the chat room that is created by the Chat user-interface (UI) control. By using Messenger Connect, you can enable a chat moderator to delete messages, view a larger message history, and block users from posting. For details, see Moderating the Chat Control.
The debugging endpoint enables developers to test their applications without limitations (or throttling) before using the production endpoint. The debugging endpoint also provides full access to all resources, so that developers can experiment to determine the appropriate offers for use in their production applications. You access the debugging endpoint by appending the letter "d" to the version number in the REST endpoint URL (http://apis.live.net/v4.1d). The debugging endpoint supports one scope: WL_Test.Full. Note that the WL_Test.Full scope is not available on the production endpoint.
The following tools and resources accompany this release:
Application management site (https://apps.dev.microsoft.com)—Use this site to register your applications with Windows Live and manage their settings. When you register your application, you receive a client ID and secret key. All programmatic interaction with Windows Live requires a client ID, which uniquely identifies your application to Windows Live. For details, see Registering Your Application with Windows Live.
Tools to help you build applications with Messenger Connect:
Based on customer feedback received during the recent beta program, we have revised the documentation for Messenger Connect scopes to make it clearer and easier to understand. For information about the scopes that are available for use in version 4.1, see Messenger Connect Scopes.