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

In this issue, the editor will bring you about what is the common namespace of ADO.NET. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

The namespace (NameSpace) records the name and path of the object. When working with objects in ADO.NET, you must first declare the namespace so that the compiler knows where to load the objects. According to the ADO.NET data provider and the main data object, the ADO.NET namespace can be divided into basic object class, data provider object class and helper object class.

System.Data: this object category address contains most of the basic ADO.NET objects, such as DataSet, DataTable, DataRow, etc., so when writing ADO.NET programs, you must declare them first.

System.Data.OLEDB: when you use the Microsoft OLE DB.NET data provider to connect to a SQL Server version 6.5 database or other database, you must first declare such objects.

System.Data.SQLClient: when you use the Microsoft SQL Server.NET data provider to connect to a SQL Server version 7. 0 database, you must first declare such objects.

System.Data.Odbc: when you use the Microsoft ODBC.NET data provider to connect to a database connected by an ODBC data source, you must first declare such objects.

System.Data.OracleClient: when you use the Oracle.NET data provider to connect to an Oracle database, you must first declare such objects.

System.Data.Common: contains classes shared by the .NET Framework data provider. A data provider describes a collection of classes used to access a data source, such as a database, in a managed space.

System.Data.Sql: a class that supports SQL Server-specific functionality.

System.Data.SqlTypes: provides classes that are used within SQL Server for native data types. These classes provide safer and faster alternatives to other data types.

Microsoft.SqlServer.Server: classes, interfaces, and enumerations dedicated to the integration of the Microsoft .NET Framework common language runtime (CLR) with the Microsoft SQL Server and SQL Server database engine process execution environments.

System.Transactions: classes that allow users to write their own transactional applications and resource managers. Specifically, you can create a transaction and participate in a transaction (local or distributed) with one or more participants.

The structure of the ADO.NET namespace is shown in the figure:

These are the common ADO.NET namespaces shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

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.