Real-Time Shared Experiences

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.

You can use the Messenger.SignIn scope to provide access to the Messenger.SignIn UI Controls and to the Windows Live Messenger context.

The resources associated with the Messenger.SignIn scope are not part of the Windows Live Messenger Connect Resource Model Structure. The Messenger.SignIn resources are supported only in the Messenger Connect JavaScript Library and cannot be accessed via the Representational State Transfer (REST) API service.

Messenger Context

You can enable user access to Messenger-specific features by using the Messenger context, which is similar in function to the Messenger Connect data context. Use the Messenger context to facilitate signing users in, and then use it (with their consent) to access their Messenger contacts, send and receive messages, and monitor online presence.

Messenger.Signin UI Controls

You can use the Messenger.SignIn user interface (UI) controls to provide a variety of Messenger-specific user experiences on a webpage, such as hosting a conversation or displaying the presence status of the user's friends. The controls are designed to work individually or in combination. For more information, see Messenger.SignIn UI Controls.

All operations begin by signing the user in. This process involves adding the Messenger.SignIn offer to your application's list of offers, and getting an instance of the Messenger context. From there, you can call the signIn method from the Messenger context instance, or you can provide an instance of the SignIn UI control or the Messenger Web Bar control for the user. For more information, see Using the Messenger Context.