Parse the formatted content by accessing the FormattedMessageParts collection. A message can consist of alert notifiers, story titles, plain text, hyperlinks, chat room links, emoticons, and downloadable file links.
Store and retrieve a bundle of user preferences for your application
This special case scenario is useful for applications that store distributed, application-specific user settings similar to those stored by the Group Chat client. It can also be used to retrieve preferences used by the Group Chat client, but the data encoded in the results is not a published format.
Connect to Group Chat.
Serialize your application’s preferences to a string, choose an identifying label, and construct an instance of GroupChatPreferenceBundle.
Invoke BeginGetPreferenceBundle(String, Int32, Boolean, AsyncCallback, Object) to retrieve the preference from the server at a later date. Supply the last known sequenceID when invoking this method. If the last known sequenceID is less than the current sequenceID stored on the server, the server will respond with new preference data. If the sequenceID matches, the server will return an empty result.
In all of the Group Chat scenarios, you are instructed to invoke the appropriate BeginXXX(...) method to perform the desired action. The arguments to this method include the callback delegate which will be invoked when the asynchronous operation is completed. Then, according to the standard IAsyncResult pattern, you invoke the matching EndXXX(...) method to retrieve the result of the operation. Group Chat API users should be familiar with the asynchronous programming pattern. For more information, see Asynchronous Programming Overview.