The CData ADO.NET Provider for Exchange gives developers the power to easily connect .NET applications to Microsoft Exchange data, including Folders, Calendar, Contacts, Tasks, and more! The Exchange Data Provider makes this Microsoft Exchange data look like SQL tables in your applications. With the CData ADO.NET Provider for Exchange developers can simply DataBind to data, just like using SQL Server. ADO.NET Provider OverviewThe Exchange ADO.NET Provider offers the most natural way to access Microsoft Exchange data from any .NET application. Simply use Exchange Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the Exchange Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc. Using the Exchange Data ProviderThe Exchange Data Provider wraps the complexity of accessing Microsoft Exchange services in an easy-to-integrate, fully managed ADO.NET Data Provider. Applications then access Microsoft Exchange through the Exchange Data Provider with simple Transact-SQL. The CData ADO.NET Provider for Exchange hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more. Working with DataAdapters, DataSets, DataTables, etc.The Exchange Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: MicrosoftExchangeConnection, MicrosoftExchangeCommand, MicrosoftExchangeDataAdapter, MicrosoftExchangeDataReader, MicrosoftExchangeDataSource, MicrosoftExchangeParameter, etc. Because of this you can now access Microsoft Exchange data in an easy, familiar way. More Than Read-Only: Full Update/CRUD SupportExchange Data Provider goes beyond read-only functionality to deliver full support for Create, Read Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the Exchange Data Provider as easily as interacting with a database table. Driver Features
|