May 2002
Beginner to intermediate
560 pages
11h 36m
English
Content preview from Essential ADO.NETBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
8.13. Implementation Alternatives: Conclusions
What are the alternatives? What is the best choice? Let's review these questions in light of the reasons for exposing data through a OLE DB provider, data provider, or Infoset provider: data exchange, integration with GUI components, and third-party product support.
Data provider writers have at least four major choices to hook into the .NET compatibility space:
Write a .NET data provider. This is a good choice for a data source (usually a relational or other database) that uses a proprietary protocol that can be parsed using a set of managed classes. The immediate example is SqlClient, which includes a TDS parser, or the OleDb data provider, which encapsulates a COM-based API. For maximum benefit ...