Managed Implementation
Topic Last Modified: 2008-08-06
This topic describes whether a technology has a managed implementation.
| Technology | Does the technology have a managed implementation? |
|---|---|
Active Directory Services Interfaces (ADSI) |
Yes (System.DirectoryServices). |
Collaboration Data Objects for Windows 2000 (CDOSYS) |
CDOSYS is an unmanaged component. The use of CDO for Windows 2000 is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework, but System.Web.Mail is the recommended way to send e-mail messages in a managed code environment. |
CDOSYS SMTP/NNTP Event Sinks |
CDOSYS is an unmanaged component. Use of CDOSYS is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. |
Collaboration Data Objects for Exchange 2000 Server (CDOEX) |
CDOEX is an unmanaged component. Use of CDOEX is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. |
Collaboration Data Objects for Exchange Management (CDOEXM) |
CDOEXM is an unmanaged component. Use if CDO for Exchange Management is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. CDOEXM can only be run on a computer on which Exchange has been installed. |
Collaboration Data Objects for Exchange Workflow (CDOWF) |
CDOWF is an unmanaged component. Use of CDOWF is not supported under the COM Interoperability layer of Visual Studio .NET. |
Exchange OLE DB Provider (ExOLEDB) |
ExOLEDB is an unmanaged component. Use of the ExOLEDB provider is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. ExOLEDB can only be run on a computer on which Exchange has been installed. |
Exchange Web Services |
Exchange Web Services are not a managed API. Client applications that use the Exchange Web Services can use managed code to consume the Web services. Managed applications typically use proxy classes generated using tools or the System.Net.HttpWebRequest and System.Net.HttpWebResponse classes from the .NET Framework. |
Exchange Store Event Sinks |
The Exchange store is not a managed application. However, it is possible to implement Exchange store event sinks in managed code, and to use the underlying ExOLEDB with COM interoperability. |
Exchange Web Forms |
The use of ASP.NET in Exchange Web forms is not supported. |
HTTP/Web Distributed Authoring and Versioning (WebDAV) |
WebDAV is not a managed IIS extension. However, client applications that use WebDAV can use managed code as appropriate. Managed applications typically use the System.Net.HttpWebRequest object from the .NET Framework. |
WebDAV Notifications |
WebDAV is not a managed IIS extension. However, client applications that use WebDAV can use managed code as appropriate. Managed applications typically use the System.Net.HttpWebRequest object from the .NET Framework. |
Incremental Change Synchronization (ICS) |
ICS is accessed as part of MAPI, and both are unmanaged components. Although MAPI can be used via a COM interoperability assembly with the .NET Framework, the ICS interfaces are not accessible via COM or automation. For this reason, only native C/C++ can be used to build applications that use ICS. |
Lightweight Directory Access Protocol (LDAP) |
LDAP is a protocol, not a component. ADSI can be used to work with LDAP-compatible directory services that are using the System.DirectoryServices .NET Framework objects. |
Messaging Application Programming Interface (MAPI) |
MAPI is an unmanaged component. Use of MAPI is not supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. MAPI can be run on many 16- and 32-bit versions of Windows. |
Outlook Object Model (OOM) |
A primary interoperability assembly enables OOM to be used in a managed-code environment. |
Outlook Web Access |
Outlook Web Access is not an API and does not provide components for use in a managed or unmanaged development environment. However, you can use the HTTPRequest and HTTPResponse managed classes to access Outlook Web Access programmatically. |
Exchange Rules |
Exchange rules COM objects are unmanaged components. Use of Exchange rules is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. |
SMTP Event Sinks |
Microsoft provides a whitepaper with code examples that detail how to write SMTP event sinks by using managed code. |
Windows Management Instrumentation (WMI) providers for Exchange |
WMI can be used in a managed-code environment, with any language that provides access to the .NET Framework. |
Exchange Backup and Restore API |
Microsoft does not support the use of the Exchange Backup and Restore API in a managed-code environment. |
Exchange writer for the Windows Volume Shadow Copy Service |
VSS cannot be used in a managed-code environment. |
See Also
Concepts
Selecting Development Technologies for Exchange
Evaluation Criteria Descriptions