| Build a Universal DAL Component |
| DotNetJunkies |
| Think about the possibilities of a component in the data access layer (DAL) of your application that didn't care what .NET Data Provider you were using. It could work just as easily with the SQL Server Data Provider or the OleDb Data Provider, or any other potential .NET Data Providers that could surface in the future. A DAL component that you could use against an Access 2000 database in development, and against a SQL Server database in production. In this tutorial, Doug shows how to build a universal data |
|
| Building a Custom Data Provider for Use with the .NET Data Access Framework |
| MSDN |
| The System.Data.dll assembly in the .NET Framework contains namespaces whose base classes can be used to create custom data providers. These namespaces also define a number of data access interfaces and base classes that let developers create data providers that will interoperate with other custom providers. Using the ADO.NET classes Connection, Command, DataReader, and DataAdapter, writing a provider is easier than writing one for OLE DB. This article explains these classes and their implementation, and how they can be used to write a variety of different kinds of data providers. |
|
| Building a Universal DAL Component |
| DotNetJunkies |
| Think about the possibilities of a component in the data access layer (DAL) of your application that didn't care what .NET Data Provider you were using. It could work just as easily with the SQL Server Data Provider or the OleDb Data Provider, or any other potential .NET Data Providers that could surface in the future. A DAL component that you could use against an Access 2000 database in development, and against a SQL Server database in production. |
|
| Data Access and Transaction Handling Framework |
| The Code Project |
| Generic data access component for different datasources, sprocs/sql, implicitly propagated transactions, explicitly managed transaction contexts etc. |
|
| Designing an Extensible DAL |
| DotNetJunkies |
| Filip walks you through how to design an extensible DAL. |
|
| Exposing Proprietary Data the .NET Way |
| MSDN |
| The .NET Framework comes with the OLE DB managed provider, which is meant to be a bridge that gives you immediate access to all the existing OLE DB providers. This component saves your current investments, as applications can continue successfully calling into existing OLE DB providers. The point, though, is another. In .NET, exposing proprietary data requires a more thoughtful choice, mostly because you have multiple and equally powerful options from which to choose.
|
|
| Generic Coding with the ADO.NET 2.0 Base Classes and Factories |
| MSDN |
| Learn more about the new functionality in ADO.NET 2.0 that enables you to create generic data access code. |
|
| Generic Data Provider |
| The Code Project |
| Generic Data Provider. An approach to make applications database independent. |
|
| Inside .NET Managed Providers |
| MSDN |
| When compared to full-fledged OLE DB providers, Microsoft .NET managed providers have a lot to offer. First off, they deliver a simplified data access architecture that often results in improved performance without the loss of functional capabilities. Furthermore, .NET managed providers directly expose provider-specific behavior to consumers through methods and properties. They also involve a much smaller set of interfaces than OLE DB providers. Last but not least, .NET managed providers work within the boundaries of the Common Language Runtime (CLR) and require no COM interaction. For SQL Server 7.0 and SQL Server 2000, the managed provider hooks up directly to the wire level, gaining a substantial performance advantage. |
|
| XmlClient Managed Provider |
| The Code Project |
| This is my first attempt at writing a Managed Provider. The idea behind it was to allow users of the Managed Provider to be able to fill DataSets from XML in a homogeneous way. This way you could mix XML and database data together without having to know exactly which is from which. |
|