What's New in the Windows Live Messenger Library
This topic summarizes the features that have been introduced in the Windows Live Messenger Library version 3.7. Version 3.7 of the Windows Live Messenger Library is fully backward compatible with earlier versions.
This topic contains the following subtopics:
The Sharing Control lets your application users share content on your site with their Windows Live contacts. Site users can select Windows Live contacts and send them a message containing a link to your site. For more information, see Sharing Control.
There are enhancements for applications that use application contacts.
Application contacts are supported regardless of the sign-in status of the site visitor. When a site visitor is unknown, or is not signed in to Messenger from the site, an application can show basic profile data of other site users who are Web Toolkit users.
A Messenger Application Key makes it possible to use application contacts without a current user (see previous bullet).
Application-specific contact properties, such as the application display picture URL.
app-contacttag to define application contact properties without programming with the Windows Live Messenger Library.
The ability to define which application contacts appear in the Contact List control and the Web Bar contact list.
An option to omit application contact list signatures.
For more information, see Application Contacts.
Integration with ASP.NET Ajax Library
The Windows Live Messenger Web Toolkit is now built with .the ASP.NET Ajax Library. With this integration, a Messenger Web Toolkit application works with the standard browser runtime library for Microsoft web development tools.
Prior to version 3.5, the Web Toolkit worked with the Script# runtime library named 'sscorlib'. See ASP.NET Ajax Library and Script# to determine whether you need to make changes to your application.
The Windows Live Messenger Web Toolkit now supports the following browsers:
Mozilla Firefox 3.5
Google Chrome 2
Users of Windows Live Messenger Web Toolkit applications should see faster page loads, sign-ins, and cross-page
Improved Browser Support
Version 3.0 supports Google Chrome and uses the postMessage feature in HTML5–enabled browsers for improved performance.
The Windows Live Messenger Library has cross-page navigation support, which enables users to navigate across pages of the same site without having to sign in again. The library uses the browser's local storage to cache the user's sign-in state in the browser. Conversations and other activities are persisted between pages. For more information about this feature, see Cross-page Navigation.
Windows Live ID Delegated Authentication
Applications can sign in users with Windows Live ID Delegated Authentication. An application can sign a user in to Windows Live Messenger through the library with a delegation token after obtaining the user's consent. For more information about this feature, see Delegated Authentication for the Windows Live Messenger Web Toolkit.
The Windows Live Messenger Library supports presence and instant messaging between Messenger users who have consented to the same application. An application can enable chat between its Messenger users, even if those users have not added each other as Messenger contacts. The users can chat without revealing their e-mail addresses. This makes it possible for users of a social networking site to chat, as long as the initiator is on the social networking site.
Applications define which application users are able to see each other's presence and chat with each other. This is done with the User.ApplicationContacts. For more information about this feature, see Application Contacts.
Application User Properties
Applications can set a display name and personal message for each signed-in application user. The application display name and personal message are propagated to all of the user's Windows Live contacts and application contacts. This makes it possible for applications to avoid making server requests to display the application-specific profile name of each user in certain scenarios.
The application user properties for contacts are available both in the Contact object and for each endpoint in the Contact.Endpoints collection. The Contact object exposes the application user properties for the application that the Windows Live Messenger Library user is signed in with. If the contact is signed in from another application, the application user properties are available in the contact's endpoint data for that application.
The Contact object supports additional properties to simplify application programming.
IsOnline: Returns whether the user is online.
IsApplicationContact: Returns whether the contact is an application contact.
ProfileUrl: Returns the URL to the user's Windows Live profile.
Adding and Finding Contacts
Users can add new Windows Live contacts without knowing their e-mail addresses. This feature is useful in conjunction with the Application Contacts feature in which two Windows Live users don't know each other's e-mail address. The application can add new contacts in this situation by using the user's CID. Applications can also search for contacts by CID through the ContactCollection.FindByCid method.
IM Address Properties
The IMAddress.Contact property returns the contact associated with an IMAddress. This feature is useful in Conversation objects where the roster contains only IMAddress objects.
ConversationCollection adds the Create(Contact) and Invite(Contact) methods to support the creation of conversations with application contacts.
The Microsoft.Live.Core.AuthenticationCompletedEventArgs object exposes additional properties to make it easier to handle different authentication states, such as whether a user is already signed in.
Messenger Script URL
The Messenger Script URL has been updated to:
|Only the version number has been incremented.|
The Contact.Presence property returns presence information for contacts. Previously, presence information was available only by using IMAddress.Presence. The Contact.Presence property can simplify application development because most applications can rely on the Contact.Presence property.
Contact Display Names
The Contact.DisplayName property returns the contact name that applications should use when they render a contact. This property is computed dynamically based on various values including the contact's current display name and the user's nickname for the contact.
Windows Live Messenger enables users to provide nicknames for their contacts. Applications can now read and write nicknames by using the Contact.Nickname property.
Showing and Hiding Sign-in Control
All collection types expose an item accessor to retrieve items from the collection. Applications no longer need to enumerate through a collection to retrieve specific items.
Mozilla Firefox 3.0 is a supported browser.