Using .NET Objects
The ADO.NET Entity Framework data provider supports the .NET public objects, exposing them as sealed objects.
For more information, see
.NET Objects Supported
.
The ADO.NET Entity Framework programming contexts inherently eliminate the need to use some ADO.NET methods and properties. These properties and methods remain useful for standard ADO.NET applications. The online help, which is integrated into Visual Studio, describes the public methods and properties of each class.
Table
24
lists the properties and methods that are not required or are implemented differently when using the data provider with an ADO.NET Entity application.
Table 24
Properties and Methods Differences with the ADO.NET Entity Data Provider
Property or Method
Behavior
PsqlCommand
AddRowID
Not supported. The ADO.NET Entity Framework does not process the additional data that is returned.
ArrayBindCount
Not supported. The application cannot influence this bind count on top of the ADO.NET Entity Framework.
ArrayBindStatus
Not supported. The application cannot influence this bind count on top of the ADO.NET Entity Framework.
BindByName
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
CommandTImeout
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
UpdatedRowSource
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
PsqlCommandBuilder
DeriveParameters
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
PsqlConnection
ConnectionTimeout
Supported only in a connection string.
StatisticsEnabled
Use the StatisticsEnabled or StatisticsDisabled stored procedure. See
Using Stored Procedures with the ADO.NET Entity Framework
for information on using this functionality in an ADO.NET Entity Framework application.
DataAdapter
UpdateBatchSize
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
Error
ErrorPosition
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.
SQLState
Not supported. Instead, the data provider uses the ADO.NET Entity Framework programming contexts.