Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

ADO.NET

From Wikipedia, the free encyclopedia
(Redirected fromADO.net)
Data access software from Microsoft .NET Framework
This article includes a list ofgeneral references, butit lacks sufficient correspondinginline citations. Please help toimprove this article byintroducing more precise citations.(March 2009) (Learn how and when to remove this message)
ADO.NET
Developer(s)Microsoft
Operating systemMicrosoft Windows
TypeSoftware framework
LicenseProprietary software (BCL portion underMIT license; source code underMs-RSL)
Websitedocs.microsoft.com/dotnet/framework/data/adonet/

ADO.NET is adata access technology from theMicrosoft.NET Framework that provides communication between relational and non-relational systems through a common set of components.[1]ADO.NET is a set of computer software components that programmers can use to access data and data services from a database. It is a part of thebase class library that is included with the Microsoft .NET Framework. It is commonly used by programmers to access and modify data stored inrelational database systems, though it can also access data in non-relational data sources. ADO.NET is sometimes considered an evolution ofActiveX Data Objects (ADO) technology, but was changed so extensively that it can be considered an entirely new product.

Architecture

[edit]
Thistechnology forms a part of.NET Framework 3.0 (having been part of the framework since version 1.0)

ADO.NET is conceptually divided into consumers and data providers.[2] The consumers are the applications that need access to the data, and the providers are the software components that implement the interface and thereby provide the data to the consumer.

Functionality exists inVisual Studio IDE to create specialized subclasses of the DataSet classes for a particulardatabase schema, allowing convenient access to each field in the schema through strongly typedproperties. This helps catch more programming errors at compile-time and enhances the IDE'sIntellisense feature.

Aprovider is a software component that interacts with adata source. ADO.NET data providers are analogous toODBC drivers,JDBC drivers, andOLE DB providers.

ADO.NET providers can be created to access such simple data stores as a text file and spreadsheet, through to such complex databases asOracle Database,Microsoft SQL Server,MySQL,PostgreSQL,SQLite,IBM Db2,Sybase ASE, and many others. They can also provide access to hierarchical data stores such as email systems.

Because different data store technologies can have different capabilities, every ADO.NET provider cannot implement every possible interface available in the ADO.NET standard. Microsoft describes the availability of an interface as "provider-specific," as it may not be applicable depending on the data store technology involved. Providers may augment the capabilities of a data store; these capabilities are known as "services" in Microsoft parlance.

Object-relational mapping

[edit]
Main article:Object-relational mapping

Entity Framework

[edit]
Main article:Entity Framework

Entity Framework (EF) is an open source object-relational mapping (ORM) framework for ADO.NET, part of .NET Framework. It is a set of technologies in ADO.NET that supports the development of data-oriented software applications. Architects and developers of data-oriented applications have typically struggled with the need to achieve two very different objectives. The Entity Framework enables developers to work with data in the form of domain-specific objects and properties, such as customers and customer addresses, without having to concern themselves with the underlying database tables and columns where this data is stored. With the Entity Framework, developers can work at a higher level of abstraction when they deal with data, and can create and maintain data-oriented applications with less code than in traditional applications.

LINQ to SQL

[edit]
Main article:LINQ to SQL

LINQ to SQL (formerly called DLINQ) allowsLINQ to be used to query Microsoft SQL Server databases, including SQL Server Compact databases. Since SQL Server data may reside on a remote server, and because SQL Server has its own query engine, it does not use the query engine of LINQ. Instead, the LINQ query is converted to a SQL query that is then sent to SQL Server for processing. Since SQL Server stores the data as relational data and LINQ works with data encapsulated in objects, the two representations must be mapped to one another. For this reason, LINQ to SQL also defines a mapping framework. The mapping is done by defining classes that correspond to the tables in the database, and containing all or a certain subset of the columns in the table as data members.

References

[edit]
  1. ^"ADO.NET Overview".docs.microsoft.com. Microsoft. Retrieved4 September 2017.
  2. ^"ADO.NET Architecture".docs.microsoft.com. Microsoft. Retrieved4 September 2017.

External links

[edit]
Wikibooks has a book on the topic of:.NET Development Foundation
Implementations
Architecture
Components
Tools
Decompilers
Obfuscators
IDEs
Organizations
Graphics and UI
Audio
Multimedia
Web
Data access
Networking
Communication
Administration and
management
Component model
Libraries
Device drivers
Security
.NET
Software factories
IPC
Accessibility
Text and multilingual
support
Authority control databases: NationalEdit this at Wikidata
Retrieved from "https://en.wikipedia.org/w/index.php?title=ADO.NET&oldid=1196426645"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp