Improvement of across times: ADO.NET Introduction (Figure) ADO.NET is an improvement in Microsoft ActiveX Data Objects (ADO) across time, which provides platform interoperability and scalable data access. Since the transmitted data is an XML format, any application that can read an XML format can perform data processing. In fact, the components that accept data are not necessarily an ADO .NET component, which can be based on a Microsoft Visual Studio solution, or any application running on other platforms. Programmable uses Visual Studio.net, you can program your object instead of a data table or a data column. ADO.NET adopts strong types of programming, which can make better expressions. For example, in the following code line, traditional programming (not strong type) if Totalcost> Table ("Customer"). Column ("Availablecredit") In this example, use associated, abstract way Program the ADO tables and columns. If you use strong types of programming, things become simpler: if Totalcost> Customer.availablecredit can be easily read in addition to convenient reading, strong type code is easier to write. In particular, dependent on statement automatic compilation, you have written objects can also be identified. As can be seen in the following example, you can easily find the table related to Customers using IntelliSense (intelligent induction) technology. Figure 1. Strong Type Programming and IntelliSense In addition, strong type data sets have higher execution speed because applications do not have to go to the ADO object collection when accessing data members. Using the Data Set (Dataset) Any of the most important thing in apps in ADO.NET is the data set. The data set refers to the copy of the database data in memory. A data set can contain any multiple data tables, each generally corresponding to tables or views in the database. The data set consists of a non-connected database data view. That is, it is not in the memory, not to maintain a activity connection with a database containing the corresponding table or view. This non-connected structural system allows only database server resources only when reading and writing the database, thereby providing better scalability. At runtime, the data takes out from the database and passed to an intermediate business object, and then proceeds to the user interface. In order to adapt to this data exchange, ADO.NET uses XML-based continuous delivery format. That is, when data is passed from one layer to another layer, the ADO.NET is scheduled to represent data in memory as XML, and then passed to other components in XML format. The figure below shows the main components in the ADO.NET solution. Figure II. ADO .NET Architecture In order to facilitate processing data, Visual Studio.net adds many new features. For advanced XML developers, Microsoft provides a color identified XML designer, which has a function of automatic compilation and label automatic compilation. Figure 3. There is a color logo, statement makeup and label complement XML designer if you want more graphic data view, developers can use the XML designer design view: Just put the data source, including Microsoft SQL Server, and Oracle Database, Drag and drop to the design interface, you can easily complete it. You can create your dataset with any data source, including XML files. Figure 4. ADO.NET Data Set Designer Usually, you need to add, modify, or delete data to develop your application. With a data preview label, you can not only add the modified data, you can also manipulate the association between data.
