ADO ADO. NET is improved by Microsoft ActiveX data Objects (ADO), which provides platform interoperability and shrinking data access capabilities. Because XML (extensible Markup Language, Extensible Markup Language) is a format for data transfer, any application that can read XML format can process the data. In fact, the receiving component does not need the ado.net component at all. It can be a solution based on Microsoft Visual Studio or any application running on any platform.
Programmable Ability
With visual Studio. NET, you can program your objects, not the tables and columns. Ado. NET uses strongly typed (strongly typed) programming techniques that highlight business objects.
For example, imagine the following line of code that uses traditional (rather than strongly typed) programming methods:
IF totalcost > Table ("Customer"). Column ("Availablecredit")
In this example, you are programming the ADO tables and columns in a relational, abstract way.
Using strongly typed programming methods, the same example is much simpler:
IF totalcost > Customer.availablecredit
In addition to being easier to read, strongly typed code is easier to write. In particular, automatic statement completion (automatic statement completion) features are sensitive to the objects you are programming. In the example below, we can navigate between the items in our dataset, and IntelliSense (IntelliSense) technology will display the available tables related to customers.
Figure 1. Strong-type programming techniques using IntelliSense
In addition, a type dataset runs faster when it is executed because the application does not need to search the ADO collection object each time it needs to access the design member.
working with data sets
The center of any software solution that uses ado.net is a dataset. The dataset is a copy of the database data in memory. A dataset includes many data tables, each of which typically corresponds to a database table or view. A dataset consists of a view of a "disconnected" database data. More precisely, the dataset exists in memory and does not have an active connection to the database that contains the table or view. This disconnected architecture uses only database server resources when reading and writing to the database, resulting in greater scalability.
At run time, the data is passed from the database to the middle-tier business object and then continues to be passed to the user interface. In order to adapt to the exchange of data ADO, ADO. NET uses a staging and transmission format based on XML. More precisely, in order to pass data from one layer to another, ADO. NET solution represents the memory data (dataset) in XML format, and then sends the XML to another component.
The following illustration shows the main components of a ado.net solution.
Figure 2. Ado. NET Architecture
In order to make it in visual Studio. NET makes it easier to use data, Visual Studio. There are many new features in net. For the core part of the XML developer, Microsoft has included a color-coded XML Designer with statement completion and identifier completion.
Figure 3. Color Coded XML Designer with statement and identifier completion
For a more graphical view of the data, developers can use the Design view of the XML Designer. You can simply drag and drop tables from any data source (including Microsoft SQL Server and Oracle databases) from the server explore onto the data surface. You can create a dataset that consists of data from multiple data sources, including any XML file.
Figure 4. Ado. NET DataSet Designer
When you design your own application, you often need to add, modify, or delete data. Using the data Preview (Preview) tab, you can not only add and modify data, but also manipulate the relationship between the data.
Figure 5. Data Preview (Preview)
Visual Studio. NET data binding technology has been greatly improved to make full use of ado.net. Creating a user interface that interacts with data is now easier. More importantly, you can now bind data to business objects and XML Web services.
