Question about Dot Net Driver terminology

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I recently became involved in an attempt to connect Asp.Net pages to an Oracle database. At the same time, I am involved in an MCAD study group. This may have lead to some confusion on my part. Please bear with me for a second.

In Chapter 5, Lesson 1 (Understanding ADO.Net) of 'Developing XML Web Services' the book appears to distinguish between conventional OLE DB and ODBC drivers, and the newer .Net Data providers.

What has me confused, when I am in Visual Studio (or other tools) and trying to setup a db connection is the list of available drivers. I see OLEDB drivers but nothing explicitly labeled as a .Net Data provider. (Or should I assume that every driver visible from Visual Studio is a .Net driver?) Could someone please shed some light on how Visual Studio handles this?
 
Hi B,

Have a look in the newsgroup

microsoft.public.dotnet.framework.adonet

Bill Vaughn and Bill Ryan (the last also active in this newsgroup) have
argued latly about that
(Both write there name as William)

Cor
I recently became involved in an attempt to connect Asp.Net pages to an
Click to expand...
Oracle database. At the same time, I am involved in an MCAD study group.
This may have lead to some confusion on my part. Please bear with me for a
second.
In Chapter 5, Lesson 1 (Understanding ADO.Net) of 'Developing XML Web
Click to expand...
Services' the book appears to distinguish between conventional OLE DB and
ODBC drivers, and the newer .Net Data providers.
What has me confused, when I am in Visual Studio (or other tools) and
Click to expand...
trying to setup a db connection is the list of available drivers. I see
OLEDB drivers but nothing explicitly labeled as a .Net Data provider. (Or
should I assume that every driver visible from Visual Studio is a .Net
driver?) Could someone please shed some light on how Visual Studio handles
this?
 
Back
Top