Languages and Tools
Languages and Tools
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. This topic provides information about how the different technologies compare with regard to Languages and Tools.
| Technology | What development languages/tools can I use? |
|---|---|
| Active Directory Services Interfaces (ADSI) | ADSI can be used with any COM/Automation-compatible languages as well as with non-COM languages such as C/C++. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | CDOSYS can be used with any COM/Automation-compatible languages as well as with non-COM languages such as C/C++. |
| CDOSYS SMTP/NNTP Event Sinks | CDOSYS can be used with any COM/Automation-compatible languages as well as with non-COM languages such as C/C++. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | CDOEX can be used with any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | CDOEXM can be used with any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | CDOWF can be used with any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| Exchange OLE DB Provider (ExOLEDB) | ExOLEDB can be used with any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| Exchange Store Event Sinks | Exchange Store Events can be implemented by using any COM/Automation-compatible language, as well as non-COM languages such as C/C++. |
| Exchange Web Forms | Exchange Web forms are HTML pages that use either the Exchange forms renderer or ASP. ASP can be written by using VBScript, Jscript, or another ASP scripting language. Client-side scripting must use a language that is compatible with the intended client. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | Because WebDAV is a protocol, any programming tool and language that correctly sends and receives HTTP requests and responses can be used to create applications that access Exchange by using WebDAV; for example, the MSXML HTTPRequest object. |
| WebDAV Notifications | Because WebDAV is a protocol, any programming tool and language that correctly sends and receives HTTP requests and responses can be used to create applications that access Exchange by using WebDAV; for example, the MSXML HTTPRequest object. |
| Incremental Change Synchronization (ICS) | Applications that use ICS can only be created by using native C/C++. |
| Lightweight Directory Access Protocol (LDAP) | LDAP is a protocol that is available through many different development tools and languages. |
| Messaging Application Programming Interface (MAPI) | You can directly access MAPI only by using C or C++. |
| Outlook Object Model (OOM) | OOM applications can be implemented by using any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| Outlook Web Access | Microsoft® Outlook® Web Access components are only available by means of HTTPS GET and POST methods. |
| Exchange Rules | Applications that define and modify Exchange rules can be implemented by using any COM/Automation-compatible language, as well as with non-COM languages such as C/C++. |
| SMTP Event Sinks | SMTP event sinks written in unmanaged code can only be written by using C and C++. |
| Windows Management Instrumentation (WMI) providers for Exchange | WMI can be used in any COM-compatible language. It is most frequently used with scripting languages such as VBScript and Jscript. Developing applications by using C/C++ is considerably more difficult than using scripting languages to develop applications. |
| Exchange Backup and Restore API | The Exchange Backup and Restore API is a non-dual dynamic-link library (DLL). For this reason, C/C++ must be used to access the backup and restore functions. Use the Microsoft Windows® LoadLibrary function to load the DLL. |
| Exchange writer for the Windows Volume Shadow Copy Service (VSS) | VSS can be used in any COM-compatible language. It is most frequently used in applications that are written in C++. Because creating shadow copies requires the Exchange store to be momentarily taken offline, backup applications are typically very time-sensitive, which in most cases prevents the use of languages like Visual Basic or VBScript. |
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: June 2006
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.