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

Designing MSN Messenger Activity Graphics

Your MSN Messenger Activity can be displayed on either the Games menu or the Activities menu in MSN® Messenger. MSN gives you the choice of using standard graphics or custom graphics for your Activity.

The following illustration shows the standard graphics available for your Activity.


If you choose, you can substitute your own graphics in place of the default activity icon or the default game icon. Adding custom graphics allows you to increase the visibility of your application, and makes it easier for your users to locate. It also provides an opportunity for you to visually identify the type of application that you are providing. However, if you choose to substitute custom graphics for your Activity, keep the following considerations in mind:

  • The custom graphics must be 20 by 20 pixels in size.
  • The custom graphics should be no more than 72 dots per inch (dpi) and no greater than 6 kilobytes (KB) in size.
  • The custom graphics should be formatted as Portable Network Graphics (PNG) files.
  • The custom graphics must be hosted on a publicly available Web server.

Note  If you design PNG graphics by using Adobe Photoshop 7.0 (or later), you must save the image in Photoshop as a transparent PNG-24 file, with the image's background layer turned off.

Implementing Custom Graphics

For your Activity to offer customized graphics, you must add the URL for the Web server (on which the graphic files are stored) to the XML file that defines your Activities' properties.

MSN Messenger adds an icon (visible to the right of your custom graphic) that lets users know whether the Activity is designed for single or multiple users. This property is controlled by the MinUsers and MaxUsers user values included in the MSGRP2P.xml file.

Note  You must submit the URL that defines the location of your custom graphics to the MSN Messenger Support team as part of the compliance process.

If you implement custom graphics, you must cache them on your Web server so that the content doesn�t expire sooner than 24 hours. The recommended value is one week. The example below provides a procedure for setting the expiration time for content on the Internet Information Services (IIS) server. If you are using Web server software from a different vendor, please review the documentation supplied by that vendor for specific caching procedures.

To enable content expiration for an IIS server

  1. Start Internet Information Services Manager.
  2. Right-click the appropriate Web site (or a subfolder within the Web site), and then click Properties.
  3. Click the HTTP Headers tab.
  4. Click the Enable Content Expiration check box.
  5. If the Expire after option is not selected, select it now.
  6. Verify that the content expiration value is set to a minimum value of 1 day. If it is not, enter the value 1 and choose 1 day(s) as the expiration value.
  7. Click OK.