By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,072 Members | 1,151 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,072 IT Pros & Developers. It's quick & easy.

Is ADO Dead (2)?

P: n/a
http://msdn.microsoft.com/library/de...etprogmsdn.asp

Introduction

In the .NET Framework, Microsoft introduces ADO.NET, an evolution of
the data access architecture provided by the Microsoft® ActiveX® Data
Objects (ADO) programming model. ADO.NET does not replace ADO for the
COM programmer; rather, it provides the .NET programmer with access to
relational data sources, XML, and application data. ADO.NET supports a
variety of development needs, including the creation of database
clients and middle-tier business objects used by applications, tools,
languages, and Internet browsers.

Built with the ADO programmer in mind, ADO.NET contains many
similarities to ADO, and also introduces several new concepts in its
design. This article addresses the most common questions the ADO
programmer encounters when first examining ADO.NET.
Overview
From its inception, ADO has provided an efficient, robust interface for

COM programmers to work with data. ADO is widely used as an interface
to a variety of different stores because it can be called from any
automation language including Microsoft Visual Basic® 6.0, Microsoft
Visual C++®, and a variety of scripting interfaces.

ADO.NET is an evolution of ADO that provides better platform
interoperability and scalable data access.

Feb 19 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.