<% order # 20 %>

The BLToolkit.DbManager component is a data provider independent wrapper for ADO.NET. It means that the DbManager does not use any specific data source classes such as SqlConnection, SqlCommand, etc. It uses common classes and interfaces instead. All data source specific logic is encapsulated in special classes called DataProviders.

The following table lists providers available with BLToolkit:

Class Provider NameNamespace Vendor
AccessDataProvider Access System.Data.OleDb Microsoft
OdbcDataProvider Odbc System.Data.Odbc Microsoft
OleDbDataProvider OleDb System.Data.OleDb Microsoft
OracleDataProvider Oracle System.Data.OracleClient Microsoft
SqlDataProvider Sql System.Data.SqlClient Microsoft
DB2DataProvider DB2 IBM.Data.DB2 IBM
FdpDataProvider Fdp FirebirdSql.Data.FirebirdClientFirebird
InformixDataProvider Informix IBM.Data.Informix IBM
MySqlDataProvider MySql MySql.Data.MySqlClient Sun Microsystems
OdpDataProvider ODP Oracle.DataAccess.Client Oracle
SqlCeDataProvider SqlCe System.Data.SqlServerCe Microsoft
SQLiteDataProvider SQLite System.Data.SQLite SQLite.org
SybaseAdoDataProviderSybaseAdoSystem.Data.OleDb Support for DataDirect Sybase ADO Provider
SybaseDataProvider Sybase Sybase.Data.AseClient Sybase

The first five providers are preregistered in the library and are ready to use. The remaining providers need additional configuration as they require references to 3rd party components.

You can add a listed above or your own data provider into your project and register it as shown below:

AddDataProvider.cs <% ..\..\..\HowTo\Data\DataProvider\AddDataProvider.cs %>

Also a data provider can be registered by configuration file:

App.config <% Doc\Data\DataProvider\App.config %> Also you can use BLToolkit config section. <% ..\..\..\UnitTests\Linq\App.config %> Here UnitTests.Linq assembly name should be replaces by your own.