Protocols/MSNP/Activities/SDK/Techref/Developing/Devintro: Difference between revisions

From NINA Wiki
Jump to navigation Jump to search
(Created automatically by Anima Importer)
 
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<!-- Generated @ 08/12/2022 23:24:08 +01:00 using Anima's CHM converter based on techref/developing/devintro.htm -->
<!-- Generated @ 08/12/2022 23:45:39 +01:00 using Anima's CHM converter based on techref/developing/devintro.htm -->
{{Protocols/MSNP|section=Activities}}
{{Protocols/MSNP|section=Activities}}
__NOTOC__= Development Considerations =  
__NOTOC__= Development Considerations =  
Line 22: Line 22:


</div>
</div>
For more information about development testing of your Activity, see [[../../techref/testing/Index|Testing an Application]].
For more information about development testing of your Activity, see [[Protocols/MSNP/Activities/SDK/Techref/Testing/Index|Testing an Application]].

Latest revision as of 00:13, 13 August 2022


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
Glossary
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
Enumerations
ConnectionType Enumeration
FileStatus Enumeration
Methods
CloseApp Method
Objects
Channel Object
Events
OnAppClose Event
OnDataError Event
OnDataReceived Event
OnFileProgress Event (Restricted)
OnFileReceived Event (Restricted)
OnIMReceived Event (Restricted)
OnRemoteAppClosed Event
OnRemoteAppLoaded Event
OnSendFileCancelled Event (Restricted)
OnTypeChanged Event
Methods
CancelSendFile Method (Restricted)
EnterIM Method (Restricted)
Initialize Method
SendData Method
SendFile Method (Restricted)
SendIM Method (Restricted)
SendIMAsUser Method (Restricted)
Properties
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
Overview
IntroductionTermsClients
Reference
Error ListCommandsRelying Party SuiteSpotlife
Services
XMPPHTTP GatewayTabsActivities
Documentation
Development ToolsMSNP Grid
PolygamyURLs used by MSN
Documents
Protocol Versions
Version 21
Version 18
Version 16
Version 15
Version 14
Version 13
Version 12
Version 11
Version 9
Version 8
Version 2
MSNC
IntroductionP2PObject DescriptorDisplay PicturesFile Transfer
Scenarios
Microsoft Messenger for Mac
MSNP on WebTV (MSNTV)

Development Considerations

Your MSN Messenger Activity is an HTML-based application that is exposed as part of the MSN® Messenger client. When developing your Activity, keep the following developmental considerations in mind:

  • The MSN Messenger client requires potential users of your Activity to have Microsoft® Internet Explorer version 5.01 installed (at a minimum).
  • The MSN Messenger client will display your Activity with a maximum window size of 500 by 500 pixels.
  • The MSN Support team requires you to include a Help link in your application so that users have easy access to assistance.
  • The Activity application programming interface (API) fixes packet size at 1,664 bytes and a maximum bandwidth of 120 packets per minute (two per second), so you may need to review bandwidth usage of your application during your application testing.
  • If your Activity requires the installation of an ActiveX® control, you must request permission from the MSN Support team before implementing this ActiveX control. The ActiveX control must also be signed. If the user chooses not to install the ActiveX control, the application must provide a clear error message.


Note  More information about ActiveX controls (including information about designing secure ActiveX controls) can be found on the ActiveX Controls page within MSDN.


For more information about development testing of your Activity, see Testing an Application.