Application Contact Properties (Messenger Connect)

Ff748846.note(en-us,MSDN.10).gifNote:
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.

Applications can access and define profile properties of application contacts.

When an application works with an application contact, it does not have access to the application contact's email address. An application can access contact properties, such as display name and status, as with any other contact.

Applications can define application-specific values for properties such as the display name for the signed-in user and the user's application contacts.

An application can use application contact properties to ensure that users see one another with user profile data that is associated with the application. For example, a user who calls himself "Bill" on Windows Live Messenger wants to use the name "Rockstar33" in an application. By setting the user's ApplicationDisplayName property to "Rockstar33", the application can ensure that all users of the application see "Rockstar33" instead of "Bill".

Applications can define the following application-specific properties for the signed-in user and for each application contact of the user.

Application-specific properties are not persisted across sessions. An application must set them every time a user signs in.

Applications can use the app-contact tag to define application-specific profile data for a signed-in user and for each application contact of the user.

The following example defines the ApplicationDisplayName and ApplicationDisplayPictureUrl for the signed-in user.

<msgr:app-contact cid='$user'
    display-name='Bill Williams'
    display-picture-url='http://example.com/img/184018401.png'>
</msgr:app-contact>

The user's display name and display picture URL are defined and sent to all contacts.

The following example defines the application display name for an application contact.

<msgr:app-contact cid='1840140810101' 
    display-name='Cindy'>
</msgr:app-contact>

This contact name appears as 'Cindy' everywhere in the application.

By default, all application contacts are displayed in the Contact List Control. You can choose which application contacts are displayed in the Contact List Control by using the Application property of the Contact object or the contact-list-enabled attribute of the Application Contact Control. You can also change the default for contact-list-enabled by setting the default-contact-list-enabled attribute of the Application Contacts Control to false. This may be useful if your application defines different levels of relationships and users want to see only specific application contacts in the contact list.

Applications can read and write contact properties in both User Authenticated Mode and Application Authenticated Mode (Messenger Connect). The properties that can be read and defined are limited to the most common profile attributes in Application Authenticated Mode. Dynamic profile attributes, such as online status, are available only in User Authenticated Mode.

Properties Available in Application Authentication Mode

The following application contact properties are available for read access:

The following application contact properties are available for write access:

Show: