2 Using the Data Providers : About the Data Providers

About the Data Providers
DataDirect Connect for ADO.NET is compliant with the Microsoft .NET Framework Versions 2.0, 3.0, 3.5, 3.5 SP1, and 4.0 and higher. DataDirect Connect for ADO.NET data providers are built with 100% managed code; they can run and connect to the database entirely within the common language runtime (CLR).
Code that runs in the native operating system, such as client libraries and COM components, is called unmanaged code. You can mix managed and unmanaged code within a single application. However, unmanaged code reaches outside the CLR, which means that it effectively increases complexity, reduces performance, and opens possible security risks.
The standard ADO.NET data providers are certified for running on the .NET Framework Versions 2.0, 3.0, 3.5, 3.5 SP1, 4.0, and 4.5. The ADO.NET Entity Framework data providers for DB2, Oracle, and Sybase support Microsoft’s ADO.NET Entity Framework, allowing you to fully leverage the functionality of this object-relational mapping tool, no matter which application development approach you use—LINQ, Entity SQL, or ADO.NET Data Services.
Figure 2-1 shows the difference between using a data provider that calls the client library and the DataDirect Connect for ADO.NET data provider that connects directly to the DBMS using wire protocol technology.
Figure 2-1. The Advantage of Using Wire ProtocolADO.NET data providers that call client pieces call unmanaged code. The DataDirect Connect for ADO.NET data providers connect to the database without calling any unmanaged code.