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:
- Download the Activity SDK from MSDN at http://msdn.microsoft.com/msn/messenger
- Develop your Activity and perform pre-review compliance testing of the application as specified in the SDK
- Submit your Activity for final review, at http://activity.msn.com before it is enabled for use by Messenger users
- Activity is reviewed based on features and review requirements
- 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.