Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "what is the use of ADO.NET data service framework". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

The ADO.NET entity Framework is designed to support data-centric applications and services and to provide a platform for programming data, raising the level of abstraction from the logical relational level to the conceptual level. By enabling developers to use data at a higher level of abstraction, the entity framework supports code independent of any particular data storage engine or relational architecture. For more information, see introduction to the entity Framework.

The entity framework supports the entity data Model (EDM) to define data and the mapping between these two levels at the storage and conceptual levels. It also enables developers to program directly data types that are defined as common language runtime (CLR) objects at the conceptual level. The entity Framework provides tools for generating EDM and related CLR objects based on existing databases. In the past, a large amount of data access code was needed to create object-based data applications and services, and these tools reduced the use of these codes and made it faster to create object-oriented data applications and services based on existing databases.

Overview of ADO.NET data Services Framework

The ADO.NET data services framework supports data services that are accessible through the standard Internet protocol (HTTP). The ADO.NET data service provides data in the form of representational state transfer (REST) resources that can be identified and addressed through URI naming conventions. According to the specification of entity data Model (EDM), data resources are defined as entities and relationships. Known formats such as JSON, AtomPub, and XML represent text-based data transferred in response to HTTP predicates (GET, PUT, POST, and DELETE).

The ADO.NET data services framework includes a server API for creating data services and a client API for implementing the programming context of queries and updates (performed by remote applications). ADO.NET data services can be used with many types of applications. Although the framework can effectively deploy data based on the entity data Model (EDM), it can also create ADO.NET data services from any data source that implements the IQueryable interface. On the client side, any application that can send HTTP requests can interact with the ADO.NET data service.

Data in relational database management system (RDBMS) can be mapped through object-relational model and deployed through ADO.NET data service, but ADO.NET data service does not require object-relational mapping. The ADO.NET data services framework can use any data source that implements IQueryable. Data services based on XML data sources, Web services, application logic, and data access technologies such as LINQ to SQL all implement EDM schemas and use query mechanisms derived from LINQ. Client applications interact with the ADO.NET data service by sending GET, PUT, POST, and DELETE requests. Data is transferred in open formats used in scripting environments, such as JSON and AtomPub. Common language Runtime (CLR) applications can reference the .NET client library (ADO.NET data Services Framework), which includes classes that create programming contexts for data queries and updates.

Create an ADO.NET data service

In the ADO.NET data services framework, there are three steps to creating a data service that supports create, read, update, and delete operations:

1. Create a data model. The ADO.NET data service will deploy a REST interface on top of the conceptual data model. The ADO.NET data service itself supports a data model based on the ADO.NET entity framework. The ADO.NET data service also provides an extension mechanism through which the data model can be deployed using common language runtime (CLR) objects. The AsQueryable method provided since Microsoft .NET Framework 3.5 effectively adds the IQueryable interface to the object that implements IEnumerable. With this new interface, you can easily deploy ADO.NET data services based on lists, arrays, and collections in .NET Framework. For more information about the data models supported by ADO.NET data services, see data models (ADO.NET data Services Framework).

two。 Create a data service. The configured data service allows the data model to be accessed through the HTTP protocol. You can also specify caching and authorization policies that are enforced by the server.

3. Select the host. The ADO.NET data service does not bind directly to network sockets, so it does not accept HTTP requests directly. Instead, they run in an existing infrastructure, such as Windows Communication Foundation.

This is the end of the content of "what is the use of the ADO.NET data Services Framework". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.