ADO.NET 2.0 broke up in pieces?
Following up some comments on this post, let me add a few more thoughts and an up-to-date list of features that will not be in ADO.NET 2.0. Of course, the list has a relative value, may be incomplete, and shouldn't be taken as an absolute truth. However, I modified the TOC of my new ASP.NET 2.0 book based on this.
Features in the PDC build that have great chances (so to speak) not to be in the final release:
- ObjectSpaces
- SQL Paging
- Server cursors (SqlResultSet class)
- Asynchronous connections
- SqlDataTable class
Features not in the PDC build that have great chances (so to speak) to be in the final release:
- Ad hoc DataSet/DataTable serialization format for .NET Remoting
- Protected (i.e., encrypted) connection strings
Features in the PDC build that have great chances (so to speak) to be in the final release:
- Asynchronous SQL commands
- SQL command sets
- Bulk copy operations
- Sizable batch updates
- Multiple Active Results sets (SQL Server 2005 only)
- Enhancements to DataTable and DataRow
AFAIK, asynchronous connections and SQL paging have been cut (for now) to better fine-tune them. Not sure about SQL Server's server cursors.
My understanding (conjecture, more precisely) is that all (most?) of these features will be released as a separate add-on a few months later, and then incorporated in a sort of 2.1 version. Remember what happened with the Oracle and ODBC .NET providers?
Late breaking news at TechED Europe. One of my talks is DAT376--What's New in ADO.NET 2.0.