From NINA Wiki
Jump to navigation Jump to search

MSNP Protocol
Activity SDK
Introduction to the MSN Messenger Activity API
Key Requirements for a MSN Messenger Activity
Introduction to MSN Messenger Activity API
Overview of MSN Messenger Activity API
Activities Menu
System Requirements
Standard vs. Advanced Applications
Supported Countries and Languages
MSN Messenger Activity API Support
Copyright Information
MSN Messenger Activity API Process
MSN Messenger Activity Process Overview
Supporting Documentation
Requesting Usage of Special Permissions
Submitting Pre-compliance Testing Results
MSN Requirements for Developing an Activity API Application
Additional Activity API Application Development Requirements
Selecting Development Options
Activity API Restrictions
Developing a MSN Messenger Activity
Development Considerations
Getting Started
Required Definitions
Document Body Basics
Single-User Application
Multiuser Application
Designing MSN Messenger Activity Graphics
Testing an Activity
Testing Overview
The Local XML File
Test Environment Setup
Increasing MSN Messenger Activity Usage
Understanding How to Increase Activity Usage with MSN
Design Considerations for Increased Activity Usage
Calling the MSN Messenger Client Directly
Calling the MSN Messenger Client from a URL
Using the MSN Messenger Variables
Technical Reference
Obtaining Access to Restricted Features
Permission Flags
ActiveX Flag
EnableIP Flag
PassportSiteID Flag
ReceiveIM Flag
ReplaceIM Flag
SendFile Flag
SendIM Flag
UserProperties Flag
The Activity Object Model
ConnectionType Enumeration
FileStatus Enumeration
CloseApp Method
Channel Object
OnAppClose Event
OnDataError Event
OnDataReceived Event
OnFileProgress Event (Restricted)
OnFileReceived Event (Restricted)
OnIMReceived Event (Restricted)
OnRemoteAppClosed Event
OnRemoteAppLoaded Event
OnSendFileCancelled Event (Restricted)
OnTypeChanged Event
CancelSendFile Method (Restricted)
EnterIM Method (Restricted)
Initialize Method
SendData Method
SendFile Method (Restricted)
SendIM Method (Restricted)
SendIMAsUser Method (Restricted)
Data Property
Error Property
FileInfo Property (Restricted)
Type Property
IM (read-only) Property (Restricted)
IM (read-write) Property (Restricted)
Error Object
Type Property
Data Property
FileInfo Object
Path Property
Size Property
Progress Property
Incoming Property
Status Property
Messenger Object
Options Method
Phone Method
User Object
EMail Property (Restricted)
GlobalIP Property (Restricted)
LocalIP Property (Restricted)
Name Property (Restricted)
PUID Property (Restricted)
Users Collection
Item Method
_NewEnum Method
Count Property
Me Property
Inviter Property
Error ListCommandsRelying Party SuiteSpotlife
XMPPHTTP GatewayTabsActivities
Development ToolsMSNP Grid
PolygamyURLs used by MSN
Protocol Versions
Version 21
Version 18
Version 16
Version 15
Version 14
Version 13
Version 12
Version 11
Version 9
Version 8
Version 2
IntroductionP2PObject DescriptorDisplay PicturesFile Transfer
Microsoft Messenger for Mac

MSN Messenger Activity Process Overview

The MSN® Messenger client (version 6.0 and later) offers extensibility features that you can use to develop a single-user or multiuser application (called an Activity).

The Activity, when it is available to customers on MSN, can be started from the Games or Activities menu on the MSN Messenger client toolbar, making your Activity available to MSN Messenger users worldwide. You can choose to limit access to just MSN subscribers, or you can target your application for specific countries that MSN serves.

The following steps explain the overall process required for you to be able to offer an Activity from the MSN Messenger client:

  1. Download the Activity SDK from MSDN at
  2. Develop your Activity and perform pre-review compliance testing of the application as specified in the SDK
  3. Submit your Activity for final review, at before it is enabled for use by Messenger users
  4. Activity is reviewed based on features and review requirements
  5. MSN notifies you when the Activity is enabled for use within Messenger

The length of time between the submittal of your Activity and the release of your Activity will vary based on a variety of factors, including whether it requires additional testing by the MSN Support team.

After the Activity is available to customers, you may need to make additional contacts with the MSN Support team for either of the following reasons:

  • The Web server that the Activity is located on needs to be taken offline for service, or for some other reason.
  • The framework of the Activity has changed, requiring you to retest the application, perform MSN pre-compliance testing again, and submit the application for compliance review again.

Framework changes include the underlying code allowing users to execute the basic functionality of the application; for example, the algorithms used to create the logic for the checkers game, or for a billing system.

Content changes involve those user interface items that may undergo change to your application (for example, during development or in production). These content changes should not involve localization issues.

Note  If your Activity undergoes nonfunctional changes (changes to the appearance of the application), you do not need to retest and recertify your Activity.