Create and use Ado.net (i) in asp.net

Ado|asp.net| the most important component in a business application is data, whether it is an online business application, a company's corporate software, or a small company's accounting application: Through a common thread and data, you must implement a fast, efficient, reliable way to store, Retrieve and process data.

The tricky thing, however, is that these data files are often stored in different formats, which requires the developer to learn to handle the exact same things in many different ways. Many data providers, such as Microsoft, strive to standardize data access formats.

From the appearance of ODBC to DAO, Rdo, OLE DB, ADO implementation, can be said that the standardization process gradually realized. In particular, the advent of ADO is a good way to achieve a universal data access model, resulting in many people think that every two years to learn a new data Access object model of the past years. But through the Internet, we find that the idea is wrong.

First, the design goal of Ado.net

As application development evolves, new applications are increasingly loosely coupled based on the WEB application model. Today, more and more applications use XML to encode data to be passed over a network connection. Web applications use HTTP as a structure for communicating between tiers, so they must explicitly handle state maintenance between requests. This new model is much different from the connected, tightly coupled programming style, which was once the hallmark of the client/server ERA. In this programming style, the connection remains open throughout the lifetime of the program without the need for special processing of the state.

The ado.net is designed to meet the requirements of this new programming model: Having fractured data structures, being able to be tightly integrated with XML, having a common data representation that combines data from multiple, different data sources, and when creating Ado.net, Microsoft has the following design goals.

Leveraging the current ADO knowledge

The ado.net design meets the many requirements of today's application development model. At the same time, the programming model is as consistent as possible with ADO, making it unnecessary for today's ADO developers to learn new data access technologies from scratch. Ado.net is an intrinsic part of the. NET Framework, so it is never completely unfamiliar to ADO programmers.

Ado.net and ADO coexist. Although most new applications based on. NET will be written using ado.net,. NET programmers can still use ADO through. NET COM Interoperability services.

Supports N-tier programming patterns
Ado.net provides best-in-class support for disconnected N-tier programming environments, and many new applications are written for that environment. The concept of using a disconnected dataset has become the focus in the programming model. The Ado.net solution for N-tier programming is the DataSet.

Integrated XML Support
XML and data access are closely linked, that is, the entire content of XML is related to data encoding, and data access more and more content is related to XML. The. NET Framework not only supports web standards, it is built entirely on web standards.

XML support is built into the very basic level of ado.net. The XML classes in the. NET Framework and Ado.net are part of the same structure and are integrated at many different levels. You do not have to choose between the data Access Service set and their XML corresponding services, which are designed to have the ability to span from one to the other.
Reference <<.net Framework SDK documentation > >