Managed Implementation
Managed Implementation
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 Managed Implementation.
| Technology | Does the technology support managed code in Visual Studio .NET? |
|---|---|
| Active Directory Services Interfaces (ADSI) | Yes (System.DirectoryServices). |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | CDOSYS is an unmanaged component. The use of CDOSYS is supported under the COM Interoperability layer of Microsoft® Visual Studio® .NET and the Microsoft .NET Framework, but the .NET Framework provided classes are the recommended way to send e-mail messages in a managed code environment. Use System.Net.Mail when using version 2.0 of the .NET Framework. Use System.Web.Mail for versions 1.0 and 1.1 of the .NET Framework. |
| CDOSYS SMTP/NNTP Event Sinks | CDOSYS is an unmanaged component. The 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. The 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. The use of CDOEXM 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. The 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. The 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 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. 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 by using the System.DirectoryServices .NET Framework objects. |
| Messaging Application Programming Interface (MAPI) | MAPI is an unmanaged component. The 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 | Microsoft 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. The use of Exchange rules is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. |
| SMTP Event Sinks | For inforamtion about and a code example for writing SMTP event sinks by using managed code, see Writing Managed Sinks for SMTP and Transport Events .gif "Online link") . |
| 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. |
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.