A byte  not GC'd but not referenced either; could it be a GC root? How?
RhetoricalRuvim - Mar 02 2019 06:47 PM
How would make this tutorial code print points incorrect order
sonar87 - Nov 03 2018 07:42 PM
set property with HTML content as string in from include not possible
LDDbyD - Oct 01 2018 06:33 AM
Recent Blog Entries
Recent Status Updates
- Managed C++
- Visual Basic 4 / 5 / 6
- linked list
- hello world
Posted 27 June 2006 - 11:19 AM
I think it is part of ASP, that is why I posted in here. Is it?
Posted 27 June 2006 - 12:53 PM
ADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and DataAdapter.
Posted 04 July 2006 - 05:47 AM
ADO (ActiveX Data Objects) is Microsoft's layer on top of OLEDB (successor to ODBC) to allow applications to talk to databases in a (somewhat) provider agnostic way. ADO is used in classic ASP, and is the source of the common ADODB.Connection, ADODB.Recordset, ADODB.Command, etc. objects that are used to interact with databases.
ADO.NET is basically the successor to ADO that runs on the .NET Framework. It's used in ASP.NET, C#, VB.NET, etc. to talk to databases. It can use "native" drivers written by application vendors, or the older OLEDB or ODBC drivers. It contains objects such as Data.OleDbCommand, OleDbConnection, DataReader, etc. As you can see, it shares some programming model similarities with ADO - but adds a bunch of new features as well.
Probably the main change in the model is that ADO.NET is designed around a disconnected model (grab the data, disconnect, work with the data, connect, and send updates) whereas ADO was designed with a connected model (open cursor on server, get first row of data, update, get second row of data, update, etc.).