is ADO.net built on top of ADO?

  • Thread starter Thread starter Allan Quatermain
  • Start date Start date
A

Allan Quatermain

Is this statement true?

"ADO.NET doesn't have it's own engine to connect to a data source, it uses
ADO internally. It's another layer on top of ADO. It's pretty much the same
as doing an interop with the ADO components... "
 
Allan Quatermain said:
Is this statement true?

"ADO.NET doesn't have it's own engine to connect to a data source, it uses
ADO internally. It's another layer on top of ADO. It's pretty much the same
as doing an interop with the ADO components... "
Click to expand...

Sounds like bollocks to me.
 
Not at all!!!
ADO.NET is based on the Disconnected Architecture and
builds on XML technology. more to follow...
 
¤ Is this statement true?
¤
¤ "ADO.NET doesn't have it's own engine to connect to a data source, it uses
¤ ADO internally. It's another layer on top of ADO. It's pretty much the same
¤ as doing an interop with the ADO components... "
¤

No ADO.NET is not a wrapper for COM based ADO.

ADO.NET can consume OLEDB (COM) and ODBC unmanaged code services (via the .NET OLEDB and ODBC
providers) but the underlying ADO.NET classes are managed and an integral part of the framework.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Allan, where did you read this? We need to make sure they stop passing
around misinformation.
While it's possible to call COM-based ADO (we call it ADO "classic" or ADOc)
from a .NET application (and this uses COM interop to access the ADO DLLs),
ADO.NET is built into the framework and uses .NET Data Providers (some of
which are built into the Framework as well) to access data.

hth

--
____________________________________
Bill Vaughn
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Thanks bill!!

William (Bill) Vaughn said:
No need for Microsoft to be bothered. It's common knowledge that it's
possible to call COM-based ADO (we call it ADO "classic" or ADOc) from a
.NET application (and this uses COM interop to access the ADO DLLs), but
ADO.NET is built into the framework and uses .NET Data Providers (some of
which are built into the Framework as well) to access data.


--
____________________________________
Bill Vaughn
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Click to expand...
 
I got this from a Asain MSDN forum. Anyway, the most important is that this
misconception doesn't get around and must be corrected.

Thanks Chap!

Allan
 
Back
Top