Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Remote Application Programming Interface (RAPI) Reference
Establishing an ActiveSync Desktop-Device Partnership
Overview of ActiveSync Programming
Creating the ActiveSync Service Provider
Managing Connection Notification, File Converters, and Partnerships
Design Guidelines for ActiveSync Synchronization Service Providers
StockPor ActiveSync Sample Application
ActiveSync Security
ActiveSync Registry Settings
ActiveSync Reference
Collapse the table of content
Expand the table of content

Remote Application Programming Interface (RAPI) Reference

Windows CE .NET

This section discusses how to use remote application programming interface (RAPI), in the Microsoft Windows CE programming environment.

Once a connection is established between a Windows CE-based device and the desktop computer, RAPI gives an application running on a desktop computer the ability to invoke function calls on a Windows CE–based platform. The desktop computer is the RAPI client and the Windows CE–based platform is the RAPI server.

The function calls behave much like the equivalent Windows CE functions. For the most part, RAPI functions have the same syntax, parameters, and return values as the corresponding Windows CE versions. RAPI functions contain a Ce prefix to differentiate them from the Windows CE functions. Any other differences are noted in the reference documentation for the RAPI functions.

Note   String and character parameters must be in Unicode format. Use the appropriate conversion routines, if necessary.

This language reference section contains descriptions of RAPI programming elements.

RAPI Functions

RAPI Interfaces

RAPI Structures


 Last updated on Thursday, April 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.

Show:
© 2015 Microsoft